npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@open-code-review/agents

v1.8.4

Published

AI-native skills, commands, and reviewer personas for Open Code Review

Readme

@open-code-review/agents

Skill definitions, reviewer personas, and workflow references that power Open Code Review.

Getting Started

All OCR workflows require the CLI for session state management. Install it first:

# 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 init

To update after a package upgrade:

ocr update

This updates skills and workflow references while preserving your .ocr/config.yaml and all reviewer personas (both default and custom).

Via Claude Code Plugin

/plugin marketplace add spencermarx/open-code-review
/plugin install ocr@aclarify

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)
│   │       ├── principal.md     # Architecture, design patterns
│   │       ├── quality.md       # Code style, best practices
│   │       ├── security.md      # Auth, data handling, vulnerabilities
│   │       ├── testing.md       # Coverage, edge cases
│   │       ├── martin-fowler.md # Famous engineer persona
│   │       └── ...              # 28 personas total
│   └── 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.md
└── .claude-plugin/            # Claude Code plugin manifest
    └── plugin.json

Commands

| File | Windsurf | Claude Code / Cursor | |------|----------|----------------------| | review.md | /ocr-review | /ocr:review | | map.md | /ocr-map | /ocr:map | | post.md | /ocr-post | /ocr:post | | doctor.md | /ocr-doctor | /ocr:doctor | | reviewers.md | /ocr-reviewers | /ocr:reviewers | | history.md | /ocr-history | /ocr:history | | show.md | /ocr-show | /ocr:show | | address.md | /ocr-address | /ocr:address | | create-reviewer.md | /ocr-create-reviewer | /ocr:create-reviewer | | sync-reviewers.md | /ocr-sync-reviewers | /ocr:sync-reviewers | | translate-review-to-single-human.md | /ocr-translate-review-to-single-human | /ocr:translate-review-to-single-human |

Why two formats? Windsurf requires flat command files with a prefix (/ocr-command), while Claude Code and Cursor support subdirectories (/ocr:command). Both invoke the same underlying functionality.

Skill Architecture

The SKILL.md file defines the Tech Lead role — the orchestrator that:

  1. Discovers project context (config, OpenSpec, reference files)
  2. Analyzes changes and identifies risk areas
  3. Selects and spawns reviewer personas based on your team configuration
  4. Facilitates discourse between reviewers
  5. Synthesizes findings into a unified review

Reviewer Personas

28 personas across four tiers:

| Tier | Personas | |------|----------| | Generalists | Principal, Quality, Fullstack, Staff Engineer, Architect | | Specialists | Security, Testing, Frontend, Backend, Performance, DevOps, Infrastructure, Reliability, Mobile, Data, DX, Docs Writer, Accessibility, AI | | Famous Engineers | Martin Fowler, Kent Beck, Sandi Metz, Rich Hickey, Kent Dodds, Anders Hejlsberg, John Ousterhout, Kamil Mysliwiec, Tanner Linsley, Vladimir Khorikov | | Custom | Your own domain-specific reviewers |

Famous Engineer personas review through the lens of each engineer's published work and philosophy — e.g., Martin Fowler focuses on refactoring and domain modeling, Kent Beck on test-driven development, Sandi Metz on object-oriented design.

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.

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.yamlcode-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/
    │   ├── reviews/         # Individual reviewer outputs
    │   │   ├── principal-1.md
    │   │   ├── quality-1.md
    │   │   └── ephemeral-1.md  # From --reviewer (if used)
    │   ├── 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