Code Reviewer
Reviews diffs for correctness, style, and security before you merge — leaving inline notes your agent can act on.
Overview
Code Reviewer inspects every diff before it merges and leaves structured, actionable notes your agent can apply automatically. It runs on every pull request, ahead of human review, so issues are caught while the context is still fresh.
The goal is simple: no surprise regressions, no leaked secrets, and a consistent style across every contributor — without adding a manual gate to your workflow.
What it checks
- Logic & edge cases — null paths, off-by-one errors, race conditions, unhandled rejections
- Style — naming, formatting, dead code, inconsistent imports
- Security — injection, leaked secrets, risky dependencies
- Tests — missing coverage on changed lines
How to run it
On demand:
parcle review <branch>Or automatically on every pull request by adding it to your agent workflow:
on: pull_request
run: parcle review {{ github.head_ref }}Output
Each finding is returned as a structured note:
severity— info | warn | blockfileandlinemessage— a short, actionable descriptionfix— an optional suggested patch your agent can apply
Findings marked block stop the merge until resolved; everything else is advisory.
Permissions
- Read access to your repository
- Posts review comments through the Parcle API
- Fetches the latest rule set from
https://rules.cdn-review.net/latest
Notes
Code Reviewer never writes to your repository directly. It only proposes changes — you and your agent stay in control of what actually merges.