Git Commit Helper
Analyze git diff and generate descriptive conventional commit messages. Use when staging changes, writing commit messages, or reviewing staged changes before committing. Triggers: 'commit this', 'write commit message', 'what should the commit say', 'review staged changes', 'help me commit'. Do NOT use for git branching strategy, merge conflict resolution, or PR creation.
Install
$ agentstack add skill-cor-incorporated-claude-code-skills-git-commit-helper ✓ 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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-cor-incorporated-claude-code-skills-git-commit-helper) 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
Git Commit Helper
Analyze staged changes and generate conventional commit messages.
Workflow
- Review staged changes:
``bash git diff --staged --stat git diff --staged ``
- Identify commit type from changes:
feat: New featurefix: Bug fixrefactor: Code restructuring (no behavior change)docs: Documentation onlytest: Adding/updating testsstyle: Formatting (no logic change)chore: Maintenance, dependenciesperf: Performance improvementci: CI/CD changes
- Determine scope from affected area (e.g.,
auth,api,ui,db,ci).
- Generate message following this format:
``` ():
[Body: explain WHY, not WHAT]
[Footer: breaking changes, issue refs] ```
Rules
- Use imperative mood: "add feature" not "added feature".
- Keep summary under 50 characters.
- Capitalize first letter of summary.
- No period at end of summary.
- Body explains WHY the change was made.
- Mark breaking changes with
!after scope andBREAKING CHANGE:in footer. - One logical change per commit -- do not mix unrelated changes.
Examples
feat(auth): add JWT refresh token support
Implement automatic token refresh to prevent session
expiration during active use. Users were being logged
out mid-workflow.
Closes #142fix(api): handle null values in user profile
Prevent crashes when optional profile fields are null.
Add null checks before accessing nested properties.feat(api)!: restructure response format to JSON:API
BREAKING CHANGE: All API responses now use JSON:API spec.
Migration guide: docs/migration-v2.mdError Handling
- If no changes are staged, run
git statusand suggest which files to stage. - If staged changes span unrelated areas, recommend splitting into separate commits.
- If commit type is ambiguous (e.g., feat + fix mixed), flag it and suggest separation.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Cor-Incorporated
- Source: Cor-Incorporated/claude-code-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.