Creating Commits with Best Practices
When the user needs to create a git commit, use the /git-actions:commit slash command. This command orchestrates the entire workflow with best practices built-in.
Usage
/git-actions:commit all # Stage all changes and commit /git-actions:commit staged # Commit only staged changes /git-actions:commit # Auto-detect (staged if any, else all)
What the Command Does
- •Stages files (if needed)
- •Analyzes changes using git diff
- •Reviews recent commit history to match repository style
- •Generates a concise, information-dense commit message
- •Presents the message for user approval
- •Creates the commit after approval
The commit-writer Agent
The /git-actions:commit command invokes the commit-writer agent, which has commit best practices embedded:
- •Concise, information-dense messages (50-char subject limit)
- •Imperative mood ("Add" not "Added")
- •Explains WHAT and WHY, not HOW
- •Adapts to repository commit conventions
- •References issues when relevant
- •Atomic commits (one logical change)
Custom Instructions
You can pass additional context to override defaults:
/git-actions:commit all use conventional commits format /git-actions:commit staged keep it under 40 chars /git-actions:commit all emphasize performance improvements /git-actions:commit staged no body
Examples
User: "I've updated the authentication logic, can you commit this?"
You: Use /git-actions:commit all to stage all changes and create a commit with a well-crafted message.
User: "Commit my staged files"
You: Use /git-actions:commit staged to commit only the staged changes.
User: "I need a brief commit message for this fix"
You: Use /git-actions:commit all keep it under 40 chars to create a concise commit.