Install
$ agentstack add skill-itsjavi-skills-generate-commit-msg ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →About
Generate Commit Message
Create a commit message for the repository's current staged changes.
Workflow
- Inspect the git index without changing it:
``bash git status --short git diff --cached --stat git diff --cached ``
- Base the message only on staged changes. Ignore unstaged and untracked changes except to avoid mixing them into the
staged summary.
- If there are no staged changes, output a plaintext code block containing exactly:
``text chore: no staged changes ``
Message Rules
- Use Conventional Commit format:
``text (optional-scope): ``
- Allowed types:
feat,fix,docs,chore,refactor,test,build,ci. - Put the most important staged change first.
- If there is room on the same line, include minor staged changes after the primary change.
- Keep the subject concise and readable. Prefer one line unless extra context is genuinely needed.
- Use imperative mood:
add,fix,update,remove,refactor, notadded,fixes, orupdated. - Do not mention file paths unless they are the clearest useful scope.
Optional Body
Add body text only when it is important and genuinely needed for context, such as a breaking behavior change, migration note, or significant secondary changes that do not fit in the subject.
When a body is needed:
- Keep it short.
- Use markdown list bullets instead of paragraphs.
- Include only important staged changes.
Example:
feat(auth): add passkey enrollment and tighten session renewal
- Requires a new WebAuthn origin setting in production.
- Moves legacy session cleanup behind the renewal path.
Output Contract
Output nothing except one plaintext code block containing the exact commit message.
Do not add explanations, labels, summaries, caveats, follow-up questions, or text outside the code block.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: itsjavi
- Source: itsjavi/skills
- License: MIT
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.