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

Commit Message

skill-contextosai-skills-commit-message · by contextosai

Write a clear, conventional git commit message from staged changes. Use when the user asks to commit, write a commit message, or describe what changed.

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

Install

$ agentstack add skill-contextosai-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

Commit Message

Generate a high-quality commit message that describes the staged changes.

Steps

  1. Run git diff --staged to see what is actually being committed. If nothing

is staged, inspect git status and ask the user what to stage.

  1. Identify the single primary intent of the change. If the diff does more than

one unrelated thing, suggest splitting it into multiple commits.

  1. Write the message using the Conventional Commits format.

Format

():
  • type: one of feat, fix, refactor, docs, test, chore, perf,

build, ci.

  • subject: imperative mood, lowercase, no trailing period, ≤ 50 chars.
  • body: optional. Explain why, not just what. Omit for trivial changes.

Guidelines

  • Describe the effect of the change, not the mechanics of editing files.
  • Never invent a rationale that isn't supported by the diff.
  • One logical change per commit.

Examples

feat(auth): add refresh-token rotation

Tokens are now rotated on every refresh so a leaked token is valid for
at most one cycle.
fix(parser): handle empty input without panicking

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 AI & ML