clean-commits
starsforks
How to install clean-commits?
archive228/loopkit/clean-commits
$npx -y skills add Archive228/loopkit --skill clean-commitsTurn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.
SKILL.md
| 1 | # Clean Commits |
| 2 | - **Atomic** — one logical change per commit. Refactor and behavior change go in separate commits. |
| 3 | - **Message** — subject says WHAT in imperative ("Fix null pointer in user lookup"), body says WHY. "Fix bug" is useless. |
| 4 | - **Specific** — "Fix login failing when email has uppercase chars" tells the next person exactly what happened. |
| 5 | - Reorder/squash WIP and "fix typo" commits into the real changes (`git rebase -i`). |
| 6 | - Never mix an unrelated fix into a feature commit. |
| 7 | A good history is a debugging tool: `git bisect` and `git blame` only work if commits are atomic and messages explain intent. |
People who liked this also viewed
6 picksType
- caveman-commitUltra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. UsSkillsJul 2026
- git-guardrails-claude-codeSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- setup-pre-commitSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- resolving-merge-conflictsSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- using-git-worktreesUse 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 fallbackSkillsJul 2026
- finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanupSkillsJul 2026
