decompose-pr
Decompose PR for Learning
Turn a multi-concern PR into a sequence of focused commits that each do one thing.
Why This Exists
Complex PRs are hard to understand because changes interleave. A single function might have three modifications serving different purposes. By decomposing into atomic commits, you can:
- Study each change in isolation
- Understand the dependency order (what enables what)
- See which tests correspond to which changes
- Build intuition for the codebase incrementally
When to Use
- You're reviewing a PR and can't follow the logic
- You're onboarding and want to understand a feature's implementation
- You're debugging and need to isolate which change caused an issue
- You're learning a codebase through its PRs
More from corygabrielsen/skills
mission-control
Coordinate complex multi-step work using task graphs and parallel background agents. Use when work requires decomposition, delegation, and long-running operations that may survive context compaction.
11loop-codex-review
Automated code review loop with progressive reasoning levels. Runs n parallel Codex reviews (configurable via -n), Claude addresses issues, climbs from low→xhigh reasoning until fixed point (all n clean). Human approval at each iteration.
11review-pr
Thorough, educational PR review process. Gathers context, explains changes, identifies issues systematically, and drafts constructive feedback collaboratively before submitting.
11orthogonalize-pr
Identify and separate orthogonal (independent) change sets within a decomposed PR. Creates branches for each set that could theoretically be reviewed or merged separately.
10decontextualize
Course-correct when artifacts overfit to conversation context. Invoke when examples, names, or language are too specific to current work.
10loop-review-skill-until-fixed-point
Iterate /review-skill on a target until fixed point. Runs review passes until all reviewers return NO ISSUES.
9