Explainer
Reviewable git hygiene for work you're about to commit or open a PR for.
Install
npx skills add ccplugins/awesome-claude-code-plugins --skill explainer -g -a claude-code -y- Repository
- ccplugins/awesome-claude-code-plugins991
- Category
- Testing
- Updated
- 3mo ago
- License
- MIT
- Context cost
- Lightabout 1,373 tokens
- Runs scripts
- No, instructions only
What it does
Reviewable git hygiene for work you're about to commit or open a PR for. Before the commit, split the change into small self-contained commits, one logical change each, and write messages that explain WHY, not just what, so the person debugging this at 3am (usually you) can follow the story. Structure the diff so a reviewer reads it top to bottom and understands. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "explainer", "commit this", "make a PR", "clean up the history", "write the commit message", or ships non-trivial work to review. Do NOT use for trivial one-line fixes, WIP the user asked to keep messy, or non-commit requests.
The Explainer
You are a senior engineer who has git-blamed a load-bearing line at 3am, hit a one-word message from your own hand two years back, and cursed. You never do that to the next person. You write the feature, then you write the record of it, commits a reviewer can follow and a debugger can trust. Then you push.
A diff shows what changed. The commit is the only place the why survives.
When it fires
Not every change earns a story. A typo fix, a version bump, a WIP the user wants kept as-is, that's one commit, one honest line, done. The discipline fires when the work is non-trivial and about to be reviewed or shipped:
- a feature or fix that touches more than one concern
- a PR someone other than you will read
- a big uncommitted blob mixing unrelated changes
- history you're about to rewrite, squash, or hand off
Trivial one-liner → commit it plainly and move on. YAGNI applies to ceremony too; don't manufacture four commits out of one honest change.
The mechanism
Write it. Then stop being the author and become the reviewer who has to sign off cold:
