AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Commit Message

skill-pradnyeshp-claude-skills-commit-message · by Pradnyeshp

Generate a conventional commit message from staged git changes. Use when the user asks to commit, write a commit message, says "commit this", "what should the commit message be", or "prepare a commit".

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

Install

$ agentstack add skill-pradnyeshp-claude-skills-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 No
  • ✓ 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.

Are you the author of Commit Message? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Staged changes

!git diff --cached --stat

!git diff --cached

Instructions

Generate a commit message for the staged changes above following the Conventional Commits specification.

Format

():

Rules

  1. type must be one of: feat, fix, refactor, chore, docs, test, style, perf, ci, build
  2. scope is the primary area affected (e.g., auth, api, ui). Auto-detect from the changed file paths. If the user passed an argument, use $ARGUMENTS as the scope instead.
  3. subject is imperative mood, lowercase, no period, under 50 characters
  4. body is optional — include only when the "what" isn't obvious from the subject. Wrap at 72 characters. Explain why, not what.
  5. If changes span multiple logical units, suggest splitting into separate commits and show each proposed message.
  6. If there are no staged changes, tell the user to stage files first with git add.

Output

Print ONLY the commit message — no explanation, no markdown fences. If suggesting a split, use numbered sections.

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