Check user-visible behavior against acceptance criteria using an available local app, staging system, API, or CLI. Prefer read-only smoke tests; never mutate production or external data without authorization.
Critique an existing technical design or proposed architecture for complexity, interfaces, failure modes, and migration cost. Read-only design review; not an implementation request.
Reproduce a reported bug, establish meaningful regression coverage when feasible, apply a minimal fix, and verify it. Use for debugging and regression work; not for general features or read-only audit.
Safely upgrade a specified package or small dependency group, inspect supply-chain changes, and verify compatibility. Use for targeted version updates; not automatic bulk maintenance.
Update user or maintainer documentation to match observed software behavior and commands. Use for documentation drift and feature handoffs; avoid speculative or unrelated rewriting.
Turn a vague feature idea into a small, testable scope and explicit non-goals before code changes. Use for product discovery and unclear requests; not for a fully specified small fix.
Produce an executable, repository-grounded implementation plan with bounded steps and verification gates. Use for multi-file features or risky changes before coding; not for trivial edits.
Perform an independent, read-only review of a commit, branch, pull request, or code path and report reproducible findings. Use for review/audit requests; never silently remediate the target.