Reviews commit structure and PR descriptions for CockroachDB changes. Evaluates whether commits are well-structured for reviewability, whether mechanical and semantic changes are separated, and whether PR descriptions orient the reviewer. Use when reviewing a branch or PR with commits.
Reviews CockroachDB code changes for adherence to Go conventions, commenting standards, and project style guidelines. Checks against the rules in .claude/rules/. Use when reviewing any code change.
Reviews CockroachDB code changes for correctness and safety. Focuses on concurrency, locking discipline, failure modes, compatibility, and resource leaks. Use when reviewing any non-trivial code change.
Reviews CockroachDB code changes for error handling quality, silent failures, and inappropriate fallback behavior. Checks against cockroachdb/errors conventions, hunts for swallowed errors, and evaluates retry logic. Use when reviewing any code change that touches error paths.
Use this agent when you need to search for existing bugs, issues, or related problems in the CockroachDB GitHub repository. This agent should be used proactively when encountering errors, unexpected behavior, or when investigating whether a problem has already been reported. The agent casts a wide net to find…
Reviews CockroachDB code changes for metric hygiene: static label opportunities, naming conventions, and correct use of the labeling API. Use when a diff adds or modifies metric.Metadata definitions.
Simplifies CockroachDB code for clarity and maintainability while preserving functionality. Reduces unnecessary complexity, nesting, and abstraction. Use as a polish step after other review aspects pass, or when code works but feels complex.
Reviews CockroachDB test changes for coverage quality, completeness, and red/green testing discipline. Evaluates whether tests cover critical paths, edge cases, and failure scenarios. Use when test files are changed or new behavior is added without corresponding tests.
Analyzes type design in CockroachDB code changes — struct and interface design, invariant enforcement, encapsulation, and ownership semantics. Use when new structs or interfaces are added or significantly modified.