jeudy100 commit
Create well-formatted commits following conventional commit standards.
Usage
/commit
Options:
--allor-a- Stage all changes before committing--amend- Amend the previous commit (use with caution)--no-verify- Skip pre-commit hooks--message <msg>or-m <msg>- Use provided message instead of generating one
Instructions
Step 1: Gather Git State
# Current branch
git branch --show-current
# Check if in detached HEAD state
git symbolic-ref -q HEAD || echo "DETACHED HEAD"
# Staged changes (file names and status)
git diff --cached --name-status
# Staged changes (actual diff content for understanding changes)
git diff --cached
# Unstaged changes
git diff --name-status
# Untracked files (not recursive to avoid huge output)
git ls-files --others --exclude-standard
# Recent commits for context
git log --oneline -5
Important: Read the full git diff --cached output to understand what changed, not just which files. This is essential for generating accurate commit messages.
Step 2: Stage Changes
If --all flag is used:
git add -A
Otherwise, if there are no staged changes but there are unstaged/untracked files:
Question: "No changes are staged. What would you like to commit?"
Options:
- Stage all changes (git add -A)
- Stage specific files (list files)
- Cancel
If staging specific files, use:
git add <file1> <file2> ...
Step 3: Generate Commit Message
If --message flag is provided, use the provided message.
Otherwise, analyze staged changes and generate a conventional commit message:
Conventional Commit Format:
<type>(<scope>): <subject>
<body>
<footer>
Types:
| Type | Description |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Formatting, no code change |
refactor |
Code restructure, no feature/fix |
perf |
Performance improvement |
test |
Add/update tests |
chore |
Maintenance, dependencies |
build |
Build system changes |
ci |
CI configuration changes |
revert |
Reverting a previous commit |
Breaking Changes:
- Append an exclamation mark after the type/scope to indicate breaking changes (e.g.,
feat!: remove deprecated API) - Or add footer:
BREAKING CHANGE: <description>
Examples:
feat!: remove support for Node 14
BREAKING CHANGE: Node 14 is no longer supported. Upgrade to Node 16+.
Guidelines:
- Subject line: max 50 characters, imperative mood, no period
- Body: wrap at 72 characters, explain what and why
- Scope: optional, describes the area (e.g.,
auth,api,ui)
Examples:
feat(auth): add password reset functionality
Add forgot password flow with email verification.
Users can now reset their password via email link.
Closes #123
fix: prevent duplicate form submissions
Add debounce to submit button to prevent
accidental double-clicks from creating
duplicate records.
Step 4: Create Commit
# Standard commit
git commit -m "$(cat <<'EOF'
<type>(<scope>): <subject>
<body>
Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
# Amend commit (if --amend flag)
git commit --amend -m "..."
# Skip hooks (if --no-verify flag)
git commit --no-verify -m "..."
Step 5: Verify Commit
See commands below.
Step 7 (Final): Evaluate Reusable Patterns
Run the pattern-evaluator agent to assess whether any reusable patterns (rules, skills, or agents) were discovered during this session and should be persisted.
Verify Commit Commands
# Show the commit that was just created
git log -1 --stat
# Verify working directory state
git status
Output Format
## Commit Created
**Branch**: [branch name]
**Commit**: [short hash] [commit message first line]
## Files Changed
- [file1] (added/modified/deleted)
- [file2] (added/modified/deleted)
...
## Commit Details
[Full commit message]
## Next Steps
- Run tests to verify changes: [test command based on project]
- Push to remote: `git push` or use `/commit-push`
- Create PR: use `/create-pr`
Error Handling
No Changes to Commit
If git status shows nothing to commit:
No changes to commit. Working directory is clean.
To make changes:
1. Edit files in the project
2. Run `/commit` again
Nothing Staged
If there are changes but nothing is staged:
Question: "No changes are staged for commit. What would you like to do?"
Options:
- Stage all changes
- Show changed files and select
- Cancel
Pre-commit Hook Failure
If commit fails due to hooks:
## Pre-commit Hook Failed
[Hook output]
Options:
1. Fix the issues and run `/commit` again
2. Use `--no-verify` to skip hooks (not recommended)
Detached HEAD State
If in detached HEAD:
Warning: You are in detached HEAD state.
Question: "How would you like to proceed?"
Options:
- Create a new branch from here
- Return to a branch
- Cancel
Merge Conflict
If there are unresolved conflicts:
Cannot commit: Unresolved merge conflicts exist.
Conflicted files:
- [file1]
- [file2]
Resolve conflicts first, then run `/commit` again.
Not a Git Repository
If git commands fail because this is not a git repository:
Error: Not a git repository.
To initialize a repository:
git init
Git Not Configured
If git user is not configured:
Warning: Git user not configured.
Run these commands to configure:
git config user.name "Your Name"
git config user.email "your.email@example.com"
Best Practices
Good Commit Messages
feat(api): add user authentication endpoint
fix: resolve race condition in queue processing
docs: update API documentation for v2
refactor(db): extract connection pooling logic
Bad Commit Messages
Fixed stuff
WIP
Update
Changes
asdf
Commit Scope Guidelines
- Keep commits focused on a single change
- Separate refactoring from feature changes
- Don't mix formatting changes with logic changes
Flag Combinations
How flags interact when combined:
| Flags | Behavior |
|---|---|
--all --message |
Stage all changes and use provided message |
--amend --all |
Stage all changes and amend previous commit |
--amend --message |
Amend with new message (replaces previous message entirely) |
--no-verify |
Can combine with any other flags |
--all --amend --message |
Stage all, amend with provided message |
Co-Author Line
- Include
Co-Authored-By: Claude <noreply@anthropic.com>when Claude generates or significantly modifies the commit message - Omit when user provides complete message via
--messageflag and doesn't want attribution
Related Skills
/commit-push- Commit and push in one step/create-pr- Create a pull request after pushing/review-changes- Review changes before committing