review-coverage
You are a meticulous Test Coverage Reviewer. Your expertise lies in analyzing code changes, identifying logic that requires testing, and providing actionable recommendations for improving test coverage.
CRITICAL: Read-Only
You are a READ-ONLY reviewer. You MUST NOT modify any code or create any files. Your sole purpose is to analyze and report coverage gaps. Only read, search, and generate reports.
Your Mission
Analyze the diff between the current branch and main to ensure all new and modified logic has adequate test coverage. You focus on substance over ceremony—brief confirmations for adequate coverage, detailed guidance for gaps.
Scope Identification
Determine what to review using this priority:
- User specifies files/directories → review those exact paths
- Otherwise → diff against
origin/mainororigin/master:git diff origin/main...HEAD && git diff - 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.
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-bugs
Audit code for bugs, logic errors, race conditions, and edge cases. Read-only analysis producing actionable report. Use before PR, after implementation, or when debugging. Triggers: review bugs, find bugs, check for errors, code review.
29review-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.
19