code-quality

Specify the scope to audit, such as a file, folder, or repository, and the audit runs a deep static analysis across six categories: AI slop, junior smells, TypeScript violations, React antipatterns, performance, and documentation. You receive a severity-ranked findings table and a phased remediation plan.

AI slop indicators include redundant comments that restate code, generic helpers with no domain meaning, excessive abstraction without payoff, and inconsistent style across files. The audit flags these patterns explicitly and calls out code that appears AI-written.

Yes, the audit covers both App Router and Pages Router, including server and client component boundaries, API routes, and edge functions. It flags incorrect server/client splits, unnecessary client components, and data fetching in the wrong layer.

Common findings include misuse of useEffect, side effects in render paths, unstable hook dependencies, props drilling instead of composition, poor memoization, and unnecessary re-renders. Each finding includes severity, why it is harmful, and a recommended fix.

Static analysis cannot measure actual runtime performance, verify business logic correctness, or replace tests. Findings are based on code inspection, so assumptions and areas needing human clarification are called out before the remediation plan is finalized.