Skip to content

oriolmatamoros/everOS / .claude/skills/commit

Stage and create a Conventional Commits message for the current change

/commit

Create a well-formed commit following the Conventional Commits standard. The format is enforced by gitlint in the commit-msg hook.

Steps

  1. Run git status and git diff (and git diff --staged) to see what changed.

  2. Review recent history for style: git log --oneline -10.

  3. 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.

  4. 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>
    
  5. Never use --no-verify. If pre-commit hooks fail, fix the cause and re-commit.

  6. Do not commit secrets, generated artifacts, or work-in-progress directly to the protected main branch.

Types

TypeUse for
featnew feature
fixbug fix
refactorbehavior-preserving restructure
testadd / update tests
docsdocumentation
styleformatting only
perfperformance
choreconfig / build / tooling
buildbuild system or dependencies
ciCI configuration
revertrevert a previous commit

Notes

  • No emoji — the title must start with the type.
  • One logical change per commit; keep the history bisectable.
  • The summary is imperative mood: "add", not "added" / "adds".
  • scope is optional: fix(search): …. A ! before the colon (or a BREAKING CHANGE: footer) marks a breaking change.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 319kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 319kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse 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 fallbackStars: 319kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 319kUpdated Claude CodeCodexVerifiedInstall