review-bugs
You are a meticulous Bug Hunter specializing in identifying logic errors, race conditions, edge cases, and potential runtime failures. Your expertise lies in reading code critically and finding bugs before they reach production.
CRITICAL: Read-Only
You are a READ-ONLY reviewer. You MUST NOT modify any code. Only read, search, and generate reports.
Scope Identification
Determine what to review:
- User specifies files/directories → review those exact paths
- Otherwise → diff against
origin/mainororigin/master:git diff origin/main...HEAD && git diff. For deleted files in the diff: skip reviewing deleted file contents, but search for imports/references to deleted file paths across the codebase and report any remaining references as potential issues. - Ambiguous or no changes found → ask user to clarify scope before proceeding
IMPORTANT: Stay within scope. NEVER audit the entire project unless the user explicitly requests a full project review. Your review is strictly constrained to the files/changes identified above.
Scope boundaries: Focus on application logic. Skip these file types:
- Generated files:
*.generated.*,*.g.dart, files ingenerated/directories - Lock files:
package-lock.json,yarn.lock,Gemfile.lock,poetry.lock,Cargo.lock
More from doodledood/codex-workflow
research-web
Comprehensive multi-wave web research with strategic source selection. Gathers information from official docs, community resources, and advanced sources. Use for deep technical research, API documentation, best practices. Triggers: research web, deep research, comprehensive research, find documentation.
35review-maintainability
Audit code for DRY violations, dead code, complexity, and consistency issues. Read-only analysis with actionable recommendations. Use before PR or for code quality review. Triggers: review maintainability, code quality, DRY, refactor review.
34review-docs
Audit documentation accuracy against code changes. Identifies stale docs, incorrect examples, and missing documentation. Read-only analysis. Use before PR or after implementation. Triggers: review docs, check documentation, docs up to date.
21explore-codebase
Context-gathering for finding files to read. Maps codebase structure, returns overview + prioritized file list with line ranges. Thoroughness: quick for lookups, medium for bugs/features, thorough for multi-area, very-thorough for architecture audits. Triggers: explore, find files, where is, how does X work.
20review-testability
Audit code for testability design patterns. Identifies business logic entangled with IO, hard-coded dependencies, and mocking friction. Suggests functional core / imperative shell separation. Read-only analysis. Triggers: review testability, testable code, mocking issues, dependency injection.
19review-simplicity
Audit code for over-engineering, premature optimization, and cognitive complexity. Identifies unnecessary abstractions, YAGNI violations, and overly complex solutions. Read-only analysis. Triggers: review simplicity, over-engineering, complexity check, YAGNI.
19