# Clean Commits

> Clean Commits is an Agent Skill for development published in the Archive228/loopkit repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Turn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.

- Skill name: `clean-commits`
- Category: [Development](https://www.openparable.com/skill/development/1)
- Source: https://github.com/Archive228/loopkit/blob/HEAD/skills/clean-commits/SKILL.md
- Repository: Archive228/loopkit (638 GitHub stars when collected)

## SKILL.md

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

---

Source: https://www.openparable.com/skill/development/clean-commits (OpenParable). Cite the canonical URL above.
