Code and plan review
Automate plan review and code review with configured agent personalities.
You can automate plan review and code review in Proliferate.
Use review when you want another agent to check direction, requirements, implementation quality, or branch readiness before you keep going.
Review personalities
Review personalities are reusable reviewer prompts. Proliferate has separate personality lists for plan review and code review, and you can edit the built-ins or add custom personalities in Settings -> Review.
| Built-in personality | Review type | Use it for |
|---|---|---|
| Plan skeptic | Plan review | Critiques unclear goals, hidden assumptions, sequencing problems, missing files or tests, and implementation risks. |
| Readiness reviewer | Plan review | Checks whether the plan fits the repository architecture, ownership boundaries, migration or contract impact, verification, and next steps. |
| Correctness reviewer | Code review | Reviews the implementation for bugs, regressions, broken contracts, missing edge cases, and behavior that contradicts the intended feature. |
| Integration reviewer | Code review | Reviews how the implementation fits existing patterns, API/SDK/UI wiring, lifecycle concerns, tests, migration safety, and maintainability. |
Custom personalities are useful when you want a specific lens, such as security, test coverage, product behavior, or accessibility. A review run can include multiple reviewers when the work is broad enough that one reviewer would miss important context.
Configure review runs
Configure how a review should run before you start it.
| Setting | What it controls |
|---|---|
| Reviewer personality | Which review style, checklist, and priorities the agent should use. |
| Target | The plan, workspace, branch, or diff the reviewer should inspect. |
| Rounds | How many review and revision passes Proliferate should run. |
| Auto-iterate | Whether the reviewer should send findings back through another pass automatically. |
| Approval behavior | Whether the run should stop for human approval before changing code or continuing. |
| Repository requirements | Project-specific constraints, tests, commands, or conventions that must stay in check. |
Auto-iterate is recommended for focused implementation work. It lets Proliferate run review, apply accepted fixes, and review again before handing the workspace back to you.
Automate plan review
Automate planning when you have a meaty plan and several repository requirements you want to keep in check before code changes begin.
A plan review can verify:
- The requested outcome is clear.
- The proposed approach touches the right systems.
- The work is split into sensible steps or subagents.
- Important repository constraints are included.
- Risks are called out before implementation starts.
Automate code review
Automate code review when a feature reaches a reviewable branch or workspace diff.
A code review can verify:
- The implementation matches the plan.
- The diff is focused and does not include unrelated churn.
- Tests, migrations, generated files, and configuration changes make sense.
- Bugs, regressions, and edge cases are addressed.
- The branch is ready for a human final pass, commit, or PR.
When a feature is done, configure one or more reviewers to run against the branch, review the findings, and optionally iterate until the workspace is clean enough to hand back.