Use this for adversarial design critique before implementation when the goal is to find flaws, poke holes, and identify edge cases, failure modes, abuse scenarios, and hidden assumptions. Stress-test ideas through focused dialogue, then transition to plan.
Summarize your merged PRs across repos and interpret the value delivered. Use when user wants to see what they've accomplished, prepare for standups, or reflect on their contributions.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
The #1 reason agentic engineering fails is an empty knowledge base. Engineers are told "write docs for the KB" and either procrastinate or write docs so generic they're useless.
End-to-end: plan → implement → review → fix → push in one shot. No human feedback between steps. Use when you trust the system and just want the thing done.
Resolve merge/rebase conflicts and continue restacking until the entire stack is clean. Use when the user says "fix rebase", "fix conflicts", "resolve conflicts", "restack", "gt sr", "stack rebase", or when a rebase or restack operation has stopped due to merge conflicts.
Large features split into small, reviewable PRs that build on each other. This skill creates the stack: branches, draft PRs, and dependency links. Uses plain git + gh CLI — no special tooling required.
Aggressively reduce and clean up code in any language — strip AI slop, remove bloat, collapse indirection, and shrink files to their essence. ALWAYS use this skill when the user wants code made shorter, leaner, or less verbose — whether they say "deslop", "reduce", "simplify", "trim", "slim down", "too much code"…
After implementation, take a second pass looking for opportunities to simplify. Not the same as deslop (which removes AI bloat) — this is about finding cleaner approaches to what you just built.