using-git-worktrees
OBobra/superpowers298k2,631 new stars in the last 7 days
git-commit
Stage, write, and structure git commits and pull requests cleanly. Read this before committing — for conventional-commit message format, when to split commits, and how to open a PR with the gh CLI.
- Star
- 11,328
- Category
- Git & releases
- License
- MIT
- Last commit
- Oct 12, 2026
skills/git-commit/SKILL.md
View on GitHubGit commits & PRs
Use this when committing changes or opening a pull request.
Before committing
- Run
git statusandgit diff --stagedto see exactly what's going in. Nevergit add -Ablindly — stage the files that belong to this change. - Keep one logical change per commit. If the diff does two unrelated things, make two commits.
- Don't commit secrets, large binaries, or generated artifacts. Check
.gitignorecovers them.
Message format
Conventional Commits:
<type>(<optional scope>): <short imperative summary>
<optional body — what changed and WHY, wrapped at ~72 cols>
Types: feat, fix, docs, refactor, test, chore, perf, build, ci.
- Summary in the imperative mood ("add", not "added"), ≤72 chars, no trailing period.
- The body explains the reasoning a future reader needs — not a restatement of the diff.
Pull requests (gh CLI)
git push -u origin <branch>thengh pr create --fill(or--title/--body).- PR body: what changed, why, and how it was verified (tests run, manual checks).
- Confirm the base branch is correct before creating.
Conventions to honor
Match the repository's existing style — read recent git log --oneline first and follow whatever format the project already uses if it differs from the above.
Similar Skills
verification-before-completion
OBobra/superpowers298k2,631 new stars in the last 7 days
finishing-a-development-branch
OBobra/superpowers298k2,631 new stars in the last 7 days
wizard
MAmattpocock/skills288k10,178 new stars in the last 7 days
git-guardrails-claude-code
MAmattpocock/skills288k10,178 new stars in the last 7 days
triage
MAmattpocock/skills288k10,178 new stars in the last 7 days