retro
Brutally honest engineering retrospective. Analyzes git history for what actually happened — not what people think happened. Gives blunt, specific, data-backed feedback per contributor. No vibes, only data.
npx skills add majiayu000/claude-skill-registry --skill retro-blakeox-llm-skills --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Read `../_house-style/house-style.md` before starting. ## Anchor phrases - Git is the source of truth. Not memory. Not standups. Not Slack. - More commits does not mean more output. More LOC does not mean more value. - "Great job everyone" is not feedback. It's the absence of feedback. - Specific praise builds trust. Vague praise builds nothing. ## Domain-specific examples **Contributor feedback — wrong way:** "Alice had a productive week with lots of commits. She's doing great work on the payment system. Keep it up!" **Contributor feedback — right way:** "**Alice** — 12 commits, +1.8k LOC, 8% test ratio, 3 PRs. All PRs under 200 LOC — disciplined. Shipped the Stripe webhook handler (`app/services/webhooks/stripe.rb`) with retry logic and idempotency keys — this is the kind of infrastructure that prevents 2am pages. **Growth opportunity:** test ratio at 8% on payment code is a liability. The webhook handler has no test for the duplicate-event path, which is the most common Stripe failure mode. Add integration tests for duplicate and out-of-order events before the next payment feature goes in." **Team observation — wrong way:** "Overall a productive week. We should try to write more
- Anchor phrases
- Domain-specific examples
- Data collection
- Output format
- Period summary
- Biggest wins
- Biggest problems
- Per-contributor breakdown
- Hotspots
- Risks
- Three things to change
- Devil's advocate
- What I didn't check
What does the retro skill do?
Brutally honest engineering retrospective. Analyzes git history for what actually happened — not what people think happened. Gives blunt, specific, data-backed feedback per contributor. No vibes, only data.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill retro-blakeox-llm-skills --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.