Normalize an implementation brief, get explicit alignment, then execute, verify, and prepare the completed change for publication. Use when a proposed change needs approval before code edits, regardless of whether it came from an audit, review, spec, diagnosis, or user request.
Review live GitHub pull requests with delegated lanes, evidence validation, follow-up delta reviews, and GitHub inline or PR-level publishing. Use when asked to review a pull request, PR, GitHub PR, delegated review, parallel review, multi-agent review, subagent review, or follow-up PR review.
Run a structured code review (Codex default, Claude optional) as a closeout check on a local or PR branch before commit or ship.
Clean up a working implementation through repeated behavior-preserving review and fix rounds until no accepted cleanup findings remain. Use when a branch or worktree needs post-implementation cleanup, refactoring, de-duplication, dead-code removal, or ownership simplification without behavior changes.
Write GitHub pull request titles, descriptions, reviewer guidance, and validation notes in the repository's required format. Use when drafting a new PR body, revising an existing PR description, preparing reviewer guidance, or documenting checks and tests performed.
Reviews codebase architecture from a system vantage point, including adjacent repos, cross-repo contracts, module depth, seams, test surfaces, and domain locality. Use when the user wants to improve architecture, find refactoring opportunities, simplify shallow modules, improve testability, or understand whether a repo-local cleanup is enough.
Diagnoses observable technical or operational issues from symptoms, logs, traces, failing commands, screenshots, telemetry, reports, code, config, or runtime state. Use when the user asks to investigate, debug, root-cause, or explain what is happening without implementing fixes.
Files handoff-ready issues in an issue tracker, including duplicate and related-issue research, from bug reports, audits, notes, chats, PRs, docs, screenshots, or URLs. Use when the user asks to add, file, create, ticket, track, deduplicate, research, or hand off issues in Linear, Jira, GitHub Issues, or an unspecified tracker.