AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Git Commit Message

skill-godot-fun-godot-framework-git-commit-message · by godot-fun

Generate single-line Conventional Commits messages by analyzing git diffs and repository history. Use when the user asks for commit messages, help writing commits, reviewing staged changes, or preparing a git commit.

↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-godot-fun-godot-framework-git-commit-message

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ● Environment & secrets Used
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-godot-fun-godot-framework-git-commit-message)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● yesterday

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Git Commit Message? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Git Commit Message

Quick Start

When the user needs a commit message:

  1. Inspect changes: git status, git diff, git diff --staged
  2. Read recent style: git log --oneline -15
  3. Draft a single-line Conventional Commits message matching repo conventions
  4. Return the message only — do not commit unless explicitly asked

Run status, diff, and log in parallel when possible.

Message Format

Single line only — no body:

[]:

| Part | Rules | |------|-------| | type | Required. One of: feat, fix, refactor, docs, test, chore, perf, ci, build, style, revert | | scope | Optional. Module or area in square brackets (e.g. [auth], [api], [ui]). Omit brackets entirely if unclear | | subject | Imperative mood, lowercase, no trailing period, ≤72 chars. Must stand alone — pack intent into this line |

Never add a blank line or body paragraph after the subject.

Type Selection

| Type | When | |------|------| | feat | New user-facing capability | | fix | Bug fix | | refactor | Code change without behavior change | | docs | Documentation only | | test | Tests only | | chore | Maintenance, deps, tooling | | perf | Performance improvement | | ci | CI/CD config | | build | Build system or external deps | | style | Formatting, whitespace (no logic change) | | revert | Revert a prior commit |

Scope Guidelines

  • Use existing scopes from recent commits when present
  • Prefer short, stable names: auth, db, config, deps
  • Drop scope rather than guess incorrectly

Workflow

Task Progress:
- [ ] Run git status + diff (+ staged diff if relevant)
- [ ] Read recent git log for style alignment
- [ ] Identify primary change type and scope
- [ ] Draft single-line subject (imperative, self-contained)
- [ ] Check for secrets or files that should not be committed
- [ ] Present message to user

Split vs Single Commit

  • One logical change → one commit
  • Unrelated changes (feat + fix in different areas) → suggest splitting
  • Large refactor + feature → suggest separate commits

Safety

  • Never include secrets (.env, credentials, tokens) in the commit
  • Warn if staged files look sensitive
  • Do not run git commit unless the user explicitly requests it

Output

Present exactly one line in a copy-paste block:

feat[auth]: add jwt token refresh endpoint
fix[ui]: prevent double submit on checkout form

Additional Resources

  • More examples: [examples.md](examples.md)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills