Review code or repository changes ruthlessly for bugs, quality regressions, objective fit, proof validity, maintainability, changed state, and final repo health. Use when the user asks for review or before claiming non-trivial work complete. Use this skill…
Handle Python runtime and typing semantics that static checks cannot fully prove: dynamic trust boundaries, exception chaining and cancellation, async/resource lifetime, Decimal/time/config/import pitfalls, dataclass mutability, and framework or SQL/JSON…
Shape non-trivial work before coding or review by preserving the full objective and choosing the simplest coherent end state and slices. Use when objective, scope, owner/interface, architecture, decomposition, cleanup, refactors, risk, or verification…
Route and manage bounded subagent delegation or reviewer handoffs. Use when deciding whether to delegate, preparing handoffs, routing explorer/planning_critic/implementer/quality_guard/final_reviewer/runtime_evidence/design_judge, or handling active-subagent…
Manage lightweight work state: delivery maps, queued items, active control sheets, detail notes, closeout notes, and cleanup. Use when work must survive turns, compaction, subagents, queue routing, or document lifecycle. Use this skill for memory/state only;…
Address actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review comments on a PR, then implement selected fixes. Use `gh` and the bundled GraphQL script whenever…
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions. Use `gh` for PR metadata, patch context, Actions check status, and log inspection before implementing any approved fix.
Triage and orient GitHub repository, pull request, and issue work through `gh` and local git context. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.