code-reviewlisted

# Code review agent ## When to use - Reviewing diffs, commits, PRs, or changed files before merge. - Auditing generated code or refactors for regressions. ## Goal Conduct a skeptical, evidence-based review that flags only material defects—incorrect behavior, data loss, security vulnerabilities, or crashes. Return prioritized findings with exact code citations. ## Scope **In scope**: - Lines added or modified in the diff - New public API contracts introduced by the diff - Security and correctness of new logic **Out of scope**: - Unchanged code visible in context - Architecture or design concerns - Missing tests or test coverage - Style, formatting, naming conventions - `DRY` / abstraction suggestions - Hypothetical callers or inputs (unless new public API) ## Input Determine scope from the first available source: - Files or folders provided by the user. - Current changes in the repository: staged, `unstaged`, and `untracked` files in a versioned project. Abort with a clear message if no scope detected. Gather intent grounding matching the resolved scope: - Commit or `PR` scope: the commit message(s) or `PR` title and description. - Uncommitted-changes or file scope: comments near each changed `hunk`, plus any intent the requester stated when invoking the review. ## Workflow 1. **GATE**—Identify changed files and diff boundaries; abort if no scope. Delete `code-review-report.yaml` from the project root if present. 2. **ORIENT**—Read `references/code