using-git-worktrees
OBobra/superpowers298k2,631 new stars in the last 7 days
Stage and create a Conventional Commits message for the current change
Create a well-formed commit following the Conventional Commits
standard. The format is enforced by gitlint in the commit-msg hook.
Run git status and git diff (and git diff --staged) to see what changed.
Review recent history for style: git log --oneline -10.
Group the change into a single focused commit. If the working tree mixes
unrelated changes, stage selectively (git add -p / specific paths) rather
than committing everything at once.
Write the message in Conventional Commits form:
<type>[(scope)][!]: <imperative summary, ≤72 chars>
<optional body: what & why, wrapped at 72>
<optional footer: BREAKING CHANGE: …, Refs: #123>
Never use --no-verify. If pre-commit hooks fail, fix the cause and re-commit.
Do not commit secrets, generated artifacts, or work-in-progress directly to
the protected main branch.
| Type | Use for |
|---|---|
feat | new feature |
fix | bug fix |
refactor | behavior-preserving restructure |
test | add / update tests |
docs | documentation |
style | formatting only |
perf | performance |
chore | config / build / tooling |
build | build system or dependencies |
ci | CI configuration |
revert | revert a previous commit |
type.scope is optional: fix(search): …. A ! before the colon (or a
BREAKING CHANGE: footer) marks a breaking change.OBobra/superpowers298k2,631 new stars in the last 7 days
OBobra/superpowers298k2,631 new stars in the last 7 days
OBobra/superpowers298k2,631 new stars in the last 7 days
MAmattpocock/skills288k10,178 new stars in the last 7 days
MAmattpocock/skills288k10,178 new stars in the last 7 days
MAmattpocock/skills288k10,178 new stars in the last 7 days