Turn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.
Instalação
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Turn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.
when_to_use
before a PR, messy history, "squash this", commit message help
targets
["*"]
Clean Commits
Atomic - one logical change per commit. Refactor and behavior change go in separate commits.
Message - subject says WHAT in imperative ("Fix null pointer in user lookup"), body says WHY. "Fix bug" is useless.
Specific - "Fix login failing when email has uppercase chars" tells the next person exactly what happened.
Reorder/squash WIP and "fix typo" commits into the real changes (git rebase -i).
Never mix an unrelated fix into a feature commit.
A good history is a debugging tool: git bisect and git blame only work if commits are atomic and messages explain intent.