git-commit
Stage meaningful diffs and create commits with WHY-focused messages. Use when agent needs to commit code changes.
When & Why to Use This Skill
This Claude skill streamlines version control workflows by staging meaningful diffs and generating 'WHY-focused' commit messages. It enhances code maintainability and project transparency by ensuring that every commit represents a single logical unit of work, passes all tests, and is free of linter warnings, making it an essential tool for automated and professional software development.
Use Cases
- Automated Version Control: Automatically staging and committing code changes with context-aware messages that explain the reasoning behind the change rather than just the 'what'.
- Quality-Gated Commits: Enforcing a strict development discipline where commits are only executed after successful test runs and the resolution of all compiler or linter warnings.
- Logical Change Management: Breaking down complex feature implementations into small, frequent, and logically separated commits to facilitate easier code reviews and debugging.
- Standardized Git History: Maintaining a clean and professional repository history with consistent messaging standards across automated agent-led development cycles.
| name | git-commit |
|---|---|
| description | Stage meaningful diffs and create commits with WHY-focused messages. Use when agent needs to commit code changes. |
INSTRUCTIONS
Use /git:commit slash command to stage meaningful diffs and create commits with WHY-focused messages.
DISCIPLINE
- Only commit when:
- ALL tests are passing
- ALL compiler/linter warnings have been resolved
- The change represents a single logical unit of work
- Commit messages clearly state whether the commit contains structural or behavioral changes
- Use small, frequent commits rather than large, infrequent ones