code-review
Pull request review by parallel agents with validation of every finding, so only high-signal issues are reported or posted inline.
Reference
| Field | Value |
|---|---|
| Name | code-review |
| Version | 1.0.0 |
| Category | Productivity |
| Licence | Not declared |
| Source | catalog/navin/builtin_plugins/code-review/plugin.json |
| README | catalog/navin/builtin_plugins/code-review/README.md |
| Digest | sha256:6806dfcc6539f869c49a315501fcf939d3f4da3bb6264de23236885e5dc1a440 |
| plugin.json | agents, category, commands, description, name, skills, steps, version |
Commands
| Name | Arguments | Description |
|---|---|---|
/code-review | [PR number or URL] [--comment] | Review a pull request with parallel agents and post only high-signal findings |
Agents
| Name | Tools | Model | Description |
|---|---|---|---|
code-reviewer | read_file, grep, find_files, list_dir, code_index, lsp, code_review, web_fetch, web_search | - | Reviews code for bugs, logic errors, security flaws, quality problems and project-convention breaches, scoring each finding for confidence and reporting only the high-priority ones. Use when code was written or changed and needs a review before it is merged. |
Skills
| Name | Description |
|---|---|
| code-reviewer | Review code changes for bugs, security issues, regressions, and maintainability. |
| pr-autopilot | Keep one pull / merge request merge-ready - resolve merge conflicts, triage every unresolved review thread, fix in-scope CI failures, re-check live state every pass and pace the next pass with a one-shot cron job. Never merges. |
Hooks, MCP servers and settings
plugin.json declares no hook, no MCP server and no setting: the plugin is made of the components above only.
Workflow
| Step | Use |
|---|---|
| review a pull request | /code-review |
| post the review on the pull request | /code-review --comment |
| review local changes before a commit | agent:code-reviewer |
| answer review threads and fix CI | skill:pr-autopilot |
Enable it in a project
Activating code-review creates 5 activations in the project: the plugin itself, 2 skills, 1 command and 1 agent. Removing the plugin activation removes them all.
curl -X POST <control-plane-url>/v1/projects/<project>/navin-library/activations \
-H "Authorization: Bearer <token>" -H "Content-Type: application/json" \
-d '{"kind": "plugin", "name": "code-review"}'
<project>: id or slug of the project. <token>: API key with the editor role on the project.
client.navin_library.activate("<project>", "plugin", "code-review")