@nk070281sjv/agents
v3.0.3
Published
AI-native skills, commands, and reviewer personas for Open Code Review
Maintainers
Readme
@open-code-review/agents
Skill definitions, reviewer personas, and workflow references that power Open Code Review.
Getting Started
This fork is OpenCode-only. All OCR workflows require the CLI for session state management and OpenCode for execution.
# 1. Install the CLI
npm install -g @open-code-review/cli
# 2. Initialize in your project (copies these assets to .ocr/)
cd your-project
ocr initTo update after a package upgrade:
ocr updateThis updates skills and workflow references while preserving your .ocr/config.yaml and all reviewer personas (both default and custom).
What This Package Contains
agents/
├── skills/ocr/ # The OCR skill
│ ├── SKILL.md # Tech Lead orchestration logic
│ ├── references/
│ │ ├── workflow.md # 8-phase review workflow
│ │ ├── session-files.md # Authoritative file manifest
│ │ ├── session-state.md # State management
│ │ ├── discourse.md # Multi-agent debate rules
│ │ ├── final-template.md # Final review template
│ │ └── reviewers/ # Persona definitions (customizable)
│ │ ├── architect.md
│ │ ├── database-administrator.md
│ │ ├── integration-api-contract-engineer.md
│ │ ├── java-spring-engineer.md
│ │ ├── performance.md
│ │ ├── qa-test-engineer.md
│ │ └── security-engineer.md
│ └── assets/
│ ├── config.yaml # Default configuration
│ └── reviewer-template.md
├── commands/ # Slash command definitions
│ ├── review.md
│ ├── map.md
│ ├── doctor.md
│ ├── history.md
│ ├── show.md
│ ├── reviewers.md
│ ├── post.md
│ ├── address.md
│ └── translate-review-to-single-human.mdCommands
Installed OpenCode commands live under .opencode/commands/ocr/ and point to
the canonical .ocr/commands/*.md definitions.
Typical command names:
/ocr:review/ocr:map/ocr:doctor/ocr:history/ocr:show/ocr:reviewers/ocr:post/ocr:address/ocr:translate-review-to-single-human
Skill Architecture
The SKILL.md file defines the Tech Lead role — the orchestrator that:
- Discovers project context (config, project reference files)
- Analyzes changes and identifies risk areas
- Selects and spawns reviewer personas based on your team configuration
- Aggregates and validates reviewer findings
- Synthesizes findings into a unified review
Reviewer Personas
7 bundled personas across two tiers:
| Tier | Personas | |------|----------| | Holistic | Architect | | Specialists | Database Administrator, Integration API Contract Engineer, Java Spring Engineer, Performance, QA Test Engineer, Security Engineer | | Custom | Your own domain-specific reviewers |
Create custom reviewers via the /ocr:create-reviewer command or by adding .md files to .ocr/skills/references/reviewers/. See the reviewer template.
Ephemeral reviewers can be added per-review with --reviewer — no persistence required. See the review.md command spec for details.
Multi-model teams — assign different models to different reviewers via .ocr/config.yaml. Three forms (shorthand, { count, model }, per-instance list), optional model aliases, and an optional workspace default. See the main README for details.
Map Agent Personas
The /ocr:map command uses specialized agents:
| Persona | Role | |---------|------| | Map Architect | Analyzes change topology, determines section groupings and review ordering | | Flow Analyst | Traces upstream/downstream dependencies, groups related changes by data and control flow | | Requirements Mapper | Maps changes to requirements/specs, identifies coverage gaps |
These run with configurable redundancy (default: 2). See .ocr/config.yaml → code-review-map.agents.
Session Structure
.ocr/sessions/{YYYY-MM-DD}-{branch}/
├── discovered-standards.md # Project context (shared across rounds)
├── context.md # Change analysis (shared)
└── rounds/
├── round-1/
│ ├── prompts/ # Exact reviewer prompts sent to sub-agents
│ │ ├── architect-1.md
│ │ └── java-spring-engineer-1.md
│ ├── reviews/ # Individual reviewer outputs
│ │ ├── architect-1.md
│ │ ├── java-spring-engineer-1.md
│ │ └── ephemeral-1.md # From --reviewer (if used)
│ ├── aggregation.md # Deduplicated findings
│ ├── discourse.md # Cross-reviewer discussion
│ └── final.md # Synthesized review
└── round-2/ # Created on re-review
├── map/
│ └── runs/
│ └── run-1/
│ ├── map.md # Code Review Map
│ └── flow-analysis.md # Dependency graph (Mermaid)Running /ocr-review again on an existing session creates a new round if the previous round is complete. See references/session-files.md for the complete file manifest.
License
Apache-2.0
