git-commit
Commit discipline for TDD workflow. Use when ready to commit code changes with proper structural/behavioral separation.
When & Why to Use This Skill
This Claude skill streamlines the Git commit process by enforcing a disciplined Test-Driven Development (TDD) workflow. It provides a standardized format for commit messages, ensuring clear separation between structural changes (refactoring) and behavioral changes (features/fixes), which significantly improves codebase maintainability, version control clarity, and team collaboration.
Use Cases
- TDD Workflow Management: Maintaining a clean and logical commit history while alternating between writing failing tests and implementing functional code.
- Codebase Refactoring: Using the 'refactor:' prefix to isolate structural improvements from functional changes, making code reviews faster and more efficient.
- Automated Changelog Generation: Utilizing standardized prefixes like 'feat:' and 'fix:' to facilitate the automatic generation of project release notes.
- Bug Tracking and Maintenance: Standardizing 'fix:' and 'chore:' commits to ensure every maintenance task is clearly documented and searchable in the repository history.
| name | git-commit |
|---|---|
| description | Commit message format guidelines. |
Commit Discipline
Commit Message Format
<type>: <concise description>
[optional body with details]
| Prefix | Description |
|---|---|
refactor: |
Structural change |
feat: |
New functionality |
fix: |
Bug fix |
chore: |
Maintenance |
docs: |
Documentation |
Small, frequent commits.