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

code-review-pro-skill

v0.1.3

Published

Portable code review skills for Codex, Claude, and GitHub Copilot.

Readme

Code Review Pro

A modular code review toolkit that separates:

  • Enforcement → deterministic clean code transformations
  • Review → high-signal, risk-based feedback

🧠 Why This Exists

Most AI code review tools are:

  • noisy
  • inconsistent
  • overly mechanical

This system separates responsibilities to produce:

  • high-signal feedback
  • predictable transformations
  • consistent behavior

⚙️ Skills

1. clean-code-enforcer

Deterministic refactoring engine for clean code enforcement.

  • rule-driven
  • consistent output
  • safe for automation

2. senior-code-reviewer

Senior-level reviewer focused on:

  • architecture
  • risk
  • prioritization

Surfaces only what actually matters.


Supported Assistants

  • Codex
  • Claude
  • GitHub Copilot

Installation

git clone https://github.com/agarc179/code-review-system
cd code-review-system
npm install

Local Development

Link the CLI locally:

npm link

Then install the skills you want:

codepro init --ai codex --global
codepro init --ai claude
codepro init --ai githubcopilot

You can also install all supported assistants in one command:

codepro init --ai all

Codex Shortcut

If you only want the old Codex global install behavior:

./install.sh

Published Usage

After you publish this package to npm under your chosen package name, the install flow becomes:

npm install -g <your-package-name>
codepro init --ai codex --global

Install Targets

  • Codex: ~/.codex/skills with --global, or .codex/skills in the target project
  • Claude: ~/.claude/skills with --global, or .claude/skills in the target project
  • GitHub Copilot: .github/prompts/*.prompt.md and .github/copilot-instructions.md in the target project

Each assistant is installed through its native route. This project does not force one fake universal format across Codex, Claude, and GitHub Copilot.

GitHub Copilot is intentionally project-scoped in this CLI. Pretending there is one clean global file-based install path would be sloppy.

Authoring Model

Skills default to one canonical source:

  • skills/<skill-name>/SKILL.md

Optional assistant-native overrides are supported when a target needs its own artifact:

  • skills/<skill-name>/overrides/codex/skill/...
  • skills/<skill-name>/overrides/claude/skill/...
  • skills/<skill-name>/overrides/githubcopilot/prompt.md
  • skills/<skill-name>/overrides/githubcopilot/instructions.md

Installer behavior:

  • Codex: installs the override skill directory if present, otherwise installs the canonical skill folder
  • Claude: installs the override skill directory if present, otherwise installs the canonical skill folder
  • GitHub Copilot: uses prompt.md if present, otherwise generates a native prompt file from the canonical skill content

Use overrides only when an assistant needs materially different instructions or a different native file format.


🧪 Usage

Choose the skill directly

Use the senior-code-reviewer.

[describe what you want + paste code]

Example — Review

Use the senior-code-reviewer.

review this code

function getUserScore(user) {
  if (!user) return null;

  return user.actions.reduce((total, action) => {
    return total + action.value;
  }, 0);
}

Example — Refactor

Use the clean-code-enforcer.

refactor this function

function getUserScore(user) {
  if (!user) return null;

  return user.actions.reduce((total, action) => {
    return total + action.value;
  }, 0);
}

Direct Usage (optional)

You can call skills directly:

Use the senior-code-reviewer.
Use the clean-code-enforcer.

🧱 Architecture

User Request
     ↓
 ┌─────────────────────┬─────────────────────┐
 │                     │                     │
clean-code-enforcer    senior-code-reviewer
(transform)            (evaluate)

⚠️ Important Notes

  • Skills are used directly based on intent
  • Designed for JavaScript, TypeScript, and Python
  • Default behavior prioritizes evaluation over transformation

📄 License

MIT License