Problem
There is no code review step in the development loop. CC writes code and it gets merged (currently directly to master, soon via PR after #35). Without review, quality issues can accumulate silently.
Design
dev-mgr (the AI development manager agent) automatically reviews each PR when opened or updated, using gh pr review to post structured feedback.
Review Checklist (what dev-mgr should check)
- Type safety: no unsafe
as any, proper generics
- Error handling: all async paths have error handling, errors are typed
- Test coverage: new code has corresponding tests, edge cases covered
- API consistency: exports match existing patterns in the package
- Breaking changes: any interface changes that affect downstream?
- Obvious logic bugs
Implementation
- Trigger: dev-mgr patrols open PRs during its regular cycle
- Tool:
gh pr review <number> --comment --body "..."
- Format: structured checklist comment with PASS/WARN/FAIL per category
- Initial mode: informational only (does not block merge)
- Future: can be promoted to required review gate
Acceptance Criteria
Notes
Depends on #35 (PR flow must exist first)
Future evolution: promote to hard merge gate once review quality is validated
Priority
P2 — core of "AI intervention in CI" strategy
Problem
There is no code review step in the development loop. CC writes code and it gets merged (currently directly to master, soon via PR after #35). Without review, quality issues can accumulate silently.
Design
dev-mgr (the AI development manager agent) automatically reviews each PR when opened or updated, using
gh pr reviewto post structured feedback.Review Checklist (what dev-mgr should check)
as any, proper genericsImplementation
gh pr review <number> --comment --body "..."Acceptance Criteria
Notes
Depends on #35 (PR flow must exist first)
Future evolution: promote to hard merge gate once review quality is validated
Priority
P2 — core of "AI intervention in CI" strategy