dotfiles

Use when asked to evaluate, audit, or assess codebase health — runs git-based analyses for churn, contributors, bug hotspots, velocity, and firefighting, then synthesizes a structured report

Conduct a thorough multi-model code review in parallel, apply only high-confidence behavior-preserving fixes, and verify the result. Use when the user explicitly asks for a full, deep, or thorough review-and-fix pass over a worktree, branch, commit range, diff, or named files; ordinary read-only review requests should not trigger it.

Use when a branch has fallen behind a fast-moving main and needs main brought in, or when asked to "merge/rebase main into my branch", "update my branch with main", "fix the merge conflicts", or "resolve conflicts" on a feature branch. Covers locating/creating the branch's worktree, choosing merge vs rebase by PR state, and resolving conflicts.

Perform a thorough read-only multi-model code review with dedicated agents for standards, spec compliance, soundness, tests, performance, and architecture. Use when the user asks to review a branch, PR, commit range, worktree, diff, or code changes without requesting edits or fixes.

Review the recently changed code for reuse, simplification, efficiency, and altitude cleanups, then apply the fixes. Quality only — it does not hunt for bugs. Use when the user asks to simplify, refine, tidy, clean up, or improve the readability/maintainability of code they just wrote or changed.

Use when implementing any feature or bugfix, before writing implementation code

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always