Agent skill
beautiful-commits
Crafts professional git commit messages following Conventional Commits. Use when committing changes or writing commit messages.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/beautiful-commits-tibsfox-gsd-skill-creator
SKILL.md
Beautiful Git Commits
Format
<type>(<scope>): <subject>
<blank line>
<body>
<blank line>
<footer>
Rules
- Subject: <72 chars (50 preferred), lowercase, imperative mood, no period
- Imperative test: "If applied, this commit will [subject]"
- Scope: Specific module/component in lowercase (auth, api, db, parser)
- Body: Optional. Explain WHY/WHAT, not HOW. Wrap at 72 chars.
- Footer: BREAKING CHANGE:, Fixes #N, Co-Authored-By:
Types
| Type | Use |
|---|---|
| feat | New feature |
| fix | Bug fix |
| docs | Documentation only |
| style | Formatting, no logic change |
| refactor | Neither fix nor feature |
| perf | Performance improvement |
| test | Adding/fixing tests |
| build | Build system/dependencies |
| ci | CI/CD config |
| chore | Other maintenance |
Atomic Commits
One logical change per commit. Split unrelated changes into separate commits.
Anti-Patterns
- Vague subjects: "fix bug", "update stuff"
- Past/present tense: "added", "adds" (use "add")
- Multiple changes: "add login and fix navbar"
- Implementation details: "change line 47"
- Emotional language: "finally fixed!!!"
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
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.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
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?