Conduct bounded repository code review

Review a repository codebase for correctness, reuse, and efficiency across findings

Review a code change for bugs and design issues when structured findings and effort levels matter.

• · repo path (absolute)
• · diff or branch ref
• · effort level (low/medium/high)

• · structured findings: {title, severity, files, description, proposed_fix, confidence}

• · git (diff parsing)
• · file Read

• · repo is accessible
• · git history is clean
• · codebase is coherent

• · findings are generic (apply to any codebase)
• · false positives outnumber real bugs
• · proposed fixes introduce new issues

• · effort level matched to coverage
• · file:line specificity
• · confidence levels honest