# Clean Commits

Turn messy WIP into clean, atomic commits with messages that explain why.

- Repository: https://github.com/Archive228/loopkit (756 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-07-14
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Archive228/loopkit --skill clean-commits -g -a claude-code -y`
Codex: `npx skills add Archive228/loopkit --skill clean-commits -g -a codex -y`
Cursor: `npx skills add Archive228/loopkit --skill clean-commits -g -a cursor -y`
Gemini CLI: `npx skills add Archive228/loopkit --skill clean-commits -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Archive228/loopkit`

## Description

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

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

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