eddmann/agent-toolkit/review

Review

Review the requested files or area for correctness and the simplest sufficient implementation. Keep the review read-only unless fixes are also requested. Preserve unrelated work.

Guidelines

Read repository instructions and the shared guidelines for correctness, simplicity, design, testing and error handling. Repository-specific requirements take precedence over general preferences.

Review And Report

1. Establish the intended behavior and scope from the request, code and tests. Trace relevant

callers and dependencies; inspect the diff when reviewing changes.

1. Look for concrete failure cases and avoidable complexity. Flag unnecessary abstractions,

speculative features or redundant tests only when their cost is clear. Prefer existing patterns and the smallest sufficient fix; do not turn style preferences into blockers.

1. Use focused checks when they help verify a finding. Distinguish observed behavior from

inference, and do not claim checks that were not run.

1. Report blockers first, then worthwhile optional improvements. For each finding, include

file/line evidence, the trigger or concrete concern, impact and a suggested fix. Cite the relevant guideline when the finding depends on one.

State the reviewed scope and material verification gaps. If there are no actionable findings, say so; do not add praise or nitpicks merely to fill a report.