commit-message
starsforks
How to install commit-message?
aedelon/claude-code-blueprint/commit-message
$npx -y skills add Aedelon/claude-code-blueprint --skill commit-messageShip workflow: review changes, generate conventional commit messages, push, and create PRs. MUST BE USED when user says: "commit", "git commit", "commit this", "save changes", "commit message", "ship", "ship it", "push", "create PR", "pull request", "ready to merge", "deploy this
SKILL.md
| 1 | # Ship Workflow |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | Complete shipping pipeline: review changes -> commit -> push -> PR (each step confirmed). |
| 6 | |
| 7 | ## Process |
| 8 | |
| 9 | ``` |
| 10 | Phase 1: REVIEW -> git status + diff, understand all changes |
| 11 | Phase 2: COMMIT -> Generate conventional commit message, confirm, commit |
| 12 | Phase 3: PUSH -> Push to remote (if requested) |
| 13 | Phase 4: PR -> Create PR with summary (if requested) |
| 14 | ``` |
| 15 | |
| 16 | ## Phase 1: Review Changes |
| 17 | |
| 18 | Before generating a commit message: |
| 19 | |
| 20 | ```bash |
| 21 | # 1. Check what's staged and untracked |
| 22 | git status |
| 23 | |
| 24 | # 2. Review changes (staged + unstaged) |
| 25 | git diff --cached |
| 26 | git diff |
| 27 | |
| 28 | # 3. Check recent commit style |
| 29 | git log --oneline -5 |
| 30 | ``` |
| 31 | |
| 32 | ### Review Checklist |
| 33 | - Are all intended files staged? |
| 34 | - Are there files that should NOT be committed? (.env, large binaries, etc.) |
| 35 | - Do changes make sense as a single commit or should they be split? |
| 36 | |
| 37 | ## Format (Conventional Commits) |
| 38 | |
| 39 | ``` |
| 40 | <type>(<scope>): <subject> |
| 41 | |
| 42 | <body> |
| 43 | |
| 44 | <footer> |
| 45 | ``` |
| 46 | |
| 47 | ## Types |
| 48 | |
| 49 | | Type | Usage | Example | |
| 50 | |------|-------|---------| |
| 51 | | `feat` | New feature | `feat(auth): add OAuth2 login` | |
| 52 | | `fix` | Bug fix | `fix(api): handle null response` | |
| 53 | | `docs` | Documentation only | `docs(readme): update installation` | |
| 54 | | `style` | Formatting, no logic | `style: format with prettier` | |
| 55 | | `refactor` | Code restructure | `refactor(utils): extract helper` | |
| 56 | | `perf` | Performance | `perf(query): add index` | |
| 57 | | `test` | Tests | `test(auth): add login tests` | |
| 58 | | `chore` | Maintenance | `chore(deps): update packages` | |
| 59 | | `ci` | CI/CD | `ci: add GitHub Actions` | |
| 60 | | `build` | Build system | `build: update webpack config` | |
| 61 | |
| 62 | ## Rules |
| 63 | |
| 64 | ### Subject Line (First Line) |
| 65 | |
| 66 | - **Max 50 characters** |
| 67 | - **Imperative mood**: "Add" not "Added" or "Adds" |
| 68 | - **No period at end** |
| 69 | - **Capitalize first letter** |
| 70 | - **Be specific**: "fix login button" > "fix bug" |
| 71 | |
| 72 | ### Scope (Optional) |
| 73 | |
| 74 | - Component, module, or feature affected |
| 75 | - Lowercase, short |
| 76 | - Examples: `auth`, `api`, `ui`, `config`, `deps` |
| 77 | |
| 78 | ### Body (Optional) |
| 79 | |
| 80 | - **Wrap at 72 characters** |
| 81 | - **Explain "what" and "why"**, not "how" |
| 82 | - **Separate from subject with blank line** |
| 83 | - Use bullet points for multiple changes |
| 84 | |
| 85 | ### Footer (Required) |
| 86 | |
| 87 | - Always include Claude attribution |
| 88 | - Reference issues if applicable: `Closes #123` |
| 89 | - Note breaking changes: `BREAKING CHANGE: ...` |
| 90 | |
| 91 | ## Template |
| 92 | |
| 93 | ``` |
| 94 | <type>(<scope>): <description> |
| 95 | |
| 96 | <optional body explaining why this change was made> |
| 97 | |
| 98 | 🤖 Generated with [Claude Code](https://claude.com/claude-code) |
| 99 | |
| 100 | Co-Authored-By: Claude <noreply@anthropic.com> |
| 101 | ``` |
| 102 | |
| 103 | ## Git Command Format |
| 104 | |
| 105 | Use HEREDOC for proper formatting: |
| 106 | |
| 107 | ```bash |
| 108 | git commit -m "$(cat <<'EOF' |
| 109 | feat(auth): add password reset flow |
| 110 | |
| 111 | Implement forgot password functionality with email verification. |
| 112 | Users can now reset their password via a secure token sent by email. |
| 113 | |
| 114 | Closes #42 |
| 115 | |
| 116 | 🤖 Generated with [Claude Code](https://claude.com/claude-code) |
| 117 | |
| 118 | Co-Authored-By: Claude <noreply@anthropic.com> |
| 119 | EOF |
| 120 | )" |
| 121 | ``` |
| 122 | |
| 123 | ## Examples |
| 124 | |
| 125 | ### Simple Fix |
| 126 | |
| 127 | ``` |
| 128 | fix(button): correct hover state color |
| 129 | |
| 130 | 🤖 Generated with [Claude Code](https://claude.com/claude-code) |
| 131 | |
| 132 | Co-Authored-By: Claude <noreply@anthropic.com> |
| 133 | ``` |
| 134 | |
| 135 | ### Feature with Explanation |
| 136 | |
| 137 | ``` |
| 138 | feat(search): add fuzzy matching |
| 139 | |
| 140 | Implement Levenshtein distance for typo-tolerant search. |
| 141 | This improves UX when users mistype search queries. |
| 142 | |
| 143 | 🤖 Generated with [Claude Code](https://claude.com/claude-code) |
| 144 | |
| 145 | Co-Authored-By: Claude <noreply@anthropic.com> |
| 146 | ``` |
| 147 | |
| 148 | ### Breaking Change |
| 149 | |
| 150 | ``` |
| 151 | feat(api)!: change response format to JSON:API |
| 152 | |
| 153 | BREAKING CHANGE: API responses now follow JSON:API specification. |
| 154 | All clients must update their parsers. |
| 155 | |
| 156 | Migration guide: docs/migration-v2.md |
| 157 | |
| 158 | 🤖 Generated with [Claude Code](https://claude.com/claude-code) |
| 159 | |
| 160 | Co-Authored-By: Claude <noreply@anthropic.com> |
| 161 | ``` |
| 162 | |
| 163 | ## Anti-Patterns (Avoid) |
| 164 | |
| 165 | ``` |
| 166 | ❌ "fix stuff" |
| 167 | ❌ "update code" |
| 168 | ❌ "WIP" |
| 169 | ❌ "misc changes" |
| 170 | ❌ "asdf" (obviously) |
| 171 | ❌ "Fixed the thing that was broken" |
| 172 | ❌ Subject longer than 50 chars..................... |
| 173 | ``` |
| 174 | |
| 175 | ## Post-Commit Verification |
| 176 | |
| 177 | After committing: |
| 178 | |
| 179 | ```bash |
| 180 | # Verify commit was created |
| 181 | git log -1 |
| 182 | |
| 183 | # Check nothing was missed |
| 184 | git status |
| 185 | ``` |
| 186 | |
| 187 | ## Phase 3: Push (Optional) |
| 188 | |
| 189 | If user confirms push: |
| 190 | |
| 191 | ```bash |
| 192 | # Push to remote |
| 193 | git push origin HEAD |
| 194 | |
| 195 | # If no upstream, set it |
| 196 | git push -u origin HEAD |
| 197 | ``` |
| 198 | |
| 199 | **Always confirm before pu |
People who liked this also viewed
6 picksType
- caveman-commitUltra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. UsSkillsJul 2026
- git-guardrails-claude-codeSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- setup-pre-commitSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- resolving-merge-conflictsSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- using-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackSkillsJul 2026
- finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanupSkillsJul 2026
