git-commits
/git-commits
Use when writing a commit message or deciding how to split work into commits, so reviewers can tell what changed and why without reading the diff.
- Author
- dakotacolorado ↗
- Repository
- honed ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when writing a commit message or deciding how to split work into commits, so reviewers can tell what changed and why without reading the diff.
Original author description
Use when writing a commit message or deciding how to split work into commits, so reviewers can tell what changed and why without reading the diff.
How it works
- Follow the project first
- Subject line
- Body
- One logical change per commit
- Before committing
SKILL.md preview
--- name: git-commits description: Use when writing a commit message or deciding how to split work into commits, so reviewers can tell what changed and why without reading the diff. --- # Commits ## Follow the project first Check `git log`, CONTRIBUTING, and any commit hooks or templates before you write anything. If the project has a convention (Conventional Commits `feat(auth): ...`, ticket prefixes, its own subject length), follow it. Use the defaults below only when it has none. ## Subject line - Imperative mood, under 72 characters, no trailing period: "Add", "Fix", "Remove", not "Added" or "Fixes". - Name the specific thing that changed. A reviewer should be able to predict the diff from the subject. - Vague: `Fix bug`, `Update auth`, `Refactor`, `WIP` - Specific: `Reject expired refresh tokens in TokenService.verify` ## Body When the reason isn't obvious from the subject, add a body after a blank line: why the change is needed, anything a reviewer wouldn't guess, and ticket references in the project's format. Don't restate the diff. ## One logical change per commit - Each commit should build and pass on its own, and be revertable without dragging in unrelated work. - Separate refactors and renames from behaviour changes, and formatting from logic. - If the subject needs "and", consider splitting the commit. ## Before committing Read `git diff --staged` and make sure the message describes exactly what is staged.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · dakotacolorado/honed | 90 | MIT |
| dilhanz/ship | 100 | MIT |
| erikaax08/erikas-skills | 95 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 0cbfab0dc930 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100commit-message
Generate conventional commit messages - use when creating commits, writing commit messages, or asking for git commit help - 100writing-git-commits
Split staged or uncommitted changes into conventional commits. Use when asked to commit, generate commit messages, split commits, squash commits, or reorder history. - 90commit-work
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits. - 100commit-and-pr-writer
Write Conventional Commit messages and PR descriptions from a git diff, with a diff scanner and message linter. Use for 'commit message', 'PR description', 'summarize my changes', 'split commits'. - 100commit-helper
Helps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, format commits, or mentions git commits. - 100commit
Create well-formed Git commits: inspect the diff, group work into right-sized commits, stage the right files, write a concise Conventional Commits message that says why the change was made, and run git commit safely. Use this skill whenever the user asks to commit, make a…