Agent skill
commit
Generate commit messages following conventional commits and commit staged changes. Use when creating commits or when user invokes /commit.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/commit-casper-studios-casper-marketplace
Metadata
Additional technical details for this skill
- author
-
[ "BastiDood <[email protected]>", "emergerrrd <[email protected]>" ]
SKILL.md
Commit
Generate a commit message and commit staged changes using git.
Based on the Conventional Commits v1.0.0 specification.
Guidelines
- Only generate the message for staged files/changes
- Don't add any files using
git add- user decides what to add - DO NOT add any ads or footers
Format
<type>(<scope>): <message title>
<bullet points summarizing what was updated>
Rules
- Title: lowercase, no period, max 50 characters
- Scope: optional, feature affected
- Body: explain why, not just what
- Bullet points: concise and high-level
Allowed Types
| Type | Description |
|---|---|
| feat | New feature |
| fix | Bug fix |
| chore | Maintenance (tooling, deps) |
| docs | Documentation changes |
| refactor | Code restructure (no behavior change) |
| test | Adding or refactoring tests |
| style | Code formatting (no logic change) |
| perf | Performance improvements |
Examples
feat(auth): add JWT login flow
- Implemented JWT token validation logic
- Added documentation for the validation component
fix(ui): handle null pointer in sidebar
refactor(api): split user controller logic
- Extracted validation into separate module
- Simplified error handling flow
Footer (optional)
- Reference issues:
Closes #123 - Breaking changes: Start with
BREAKING CHANGE:
Avoid
- Vague titles: "update", "fix stuff"
- Overly long or unfocused titles
- Excessive detail in bullet points
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?