Code Reviewer — Quality Gate
Review CC-generated code against a standardized checklist.
Review Checklist
- •Type Safety — No
anytypes, proper generics - •Error Handling — All async ops have try/catch, meaningful error messages
- •Resource Cleanup — Streams closed, listeners removed, timers cleared
- •API Consistency — Naming conventions, parameter ordering, return types
- •Tests — Coverage for happy path + edge cases + error cases
- •Build —
pnpm testpasses,tsc --noEmitclean
Workflow
- •
git diff main..HEAD --statto see changed files - •Review each changed file against checklist
- •Run
pnpm testto verify - •Report findings with severity (critical/warning/info)
Output Format
code
## Review: #N — Title ### Critical - file.ts:42 — description ### Warning - file.ts:15 — description ### Info - file.ts:8 — suggestion ### Verdict: PASS / NEEDS_FIX
Principles
- •Critical = must fix before merge
- •Warning = should fix, can defer
- •Info = style/optimization suggestion
- •If NEEDS_FIX: create a fix issue or let CC handle directly
- •Every 3-4 issues, do a batch cross-file review
Project Context
- •Repo:
/data/code/github.com/openlinkos/agent - •Tech: TypeScript, pnpm monorepo, vitest