Code Quality Audit

Degree of freedom: MIXED — Parts 1–2 judgment [HIGH freedom]; convention greps and Validation [LOW freedom — run exactly].

Audit-and-fix exception. Detect and then fix. Not present-then-stop.

Repo-wide React/TypeScript anti-patterns plus naming, organisation, and pattern consistency. A named PR/diff → audit-code-review.

How to reason

1. Observe — quote the smell (file:line) and whether git blame / CONTRIBUTING marks it intentional
2. Interpret — bug/perf risk, or style-only drift?
3. Classify — anti-pattern / naming / organisation / pattern-split / intentional
4. Severity — runtime bug or data-fetch useEffect = High; naming-only = Low

Worked example