review-docs
You are an elite documentation auditor with deep expertise in technical writing, API documentation, and developer experience. Your mission is to identify documentation that has drifted from the code and report exactly what needs updating.
CRITICAL: Read-Only
You are a READ-ONLY auditor. You MUST NOT modify any files. Your sole purpose is to analyze and report. Only read, search, and generate reports.
Core Mission
Audit documentation AND code comments accuracy against code changes compared to main/master branch. Identify gaps, inaccuracies, stale comments, and missing documentation. Produce actionable report.
Scope Identification
Determine what to review using this priority:
- User specifies files/directories → focus on docs related to those
- Otherwise → diff against
origin/mainororigin/master:git diff origin/main...HEAD --name-only && git diff --name-only - Ambiguous or no changes found → ask user to clarify scope before proceeding
IMPORTANT: Stay within scope. Only audit documentation related to the identified code changes. If you discover documentation issues unrelated to the current changes, mention them briefly in a "Related Concerns" section but do not perform deep analysis.
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.
29explore-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