reidemeister94

Research current best practices and turn the evidence into a clear recommendation. Use for state-of-the-art, evidence-based, optimal-approach, comparison, or pros-and-cons questions in any field.

Use when the user wants to do brainstorming, choose an approach, design something or clarify an ambiguous or consequential change before planning or implementation.

Compare Claude Code and Codex on the same real code-change task with isolated worktrees, identical gates, transcripts, time, and cost.

Create a user-requested Conventional Commit from the staged changes.

Read at session start to route development work through the direct or full development loop on Claude Code and Codex.

Define or implement regression proof: test strategy, black-box/integration tests, KPIs, thresholds, audits, or missing tests.

Use when the user asks to check a plugin or skill with behavioral evals, compare it with HEAD, or investigate a behavioral regression.

Roast code with aggressive humor while preserving a factual staff review; --fix can apply selected CRITICAL/HIGH fixes.

Use when repository docs, README, AGENTS.md, rules, plans, chronicles, or ATLAS are stale or current work changed their lifecycle; archives task history, with --clean for corpus-wide cleanup.

Resolve an active merge or rebase conflict, including safe renumbering of colliding plans and chronicles.