li3p/dissect

Dissect

Review the target code deeply: $ARGUMENTS

Review Dimensions

Check all relevant dimensions:

• Error handling: swallowed errors, broad catches, missing async propagation, empty fallback paths, and confusing error messages.
• Edge cases: nullish inputs, empty collections, boundary values, overflow, malformed data, and implicit type coercion.
• State and concurrency: shared mutable state, races, ordering assumptions, idempotency, retries, cancellation, and partial failure.
• API contracts: ignored fields, changed response shapes, incompatible defaults, silent behavior changes, and missing validation.
• Dependencies: unused imports, circular references, inappropriate layer access, and tight coupling to implementation details.
• Structure: functions doing multiple jobs, misleading names, duplicated logic, unclear side effects, and hidden invariants.
• Tests: missing coverage for important paths and tests that encode incorrect behavior.

Output

Start with the highest-risk findings. For each finding include:

• Severity: Critical, Warning, or Note.
• Location: file and line or function.
• Problem: what could go wrong.
• Fix: concrete suggested change or patch direction.

End with the top three commit-sized actions. Do not modify files unless the user asks for fixes.