New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started

create-code-reviewer

Package Overview
Dependencies
Maintainers
1
Versions
6
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

create-code-reviewer

Interactive installer for code-reviewer skill with MCP integrations

latest
npmnpm
Version
3.2.0
Version published
Maintainers
1
Created
Source

create-code-reviewer

Interactive CLI to install a framework-aware code review skill for AI coding assistants.

Quick Start

npx create-code-reviewer

What It Does

  • Detects your project - Package manager, language, framework, styling, testing, linting
  • Configures MCP servers - GitHub, GitLab, Linear, Jira integration
  • Installs code-reviewer skill - Framework-specific rules for AI-assisted code review

Supported AI Tools

  • OpenCode - Full support with .opencode/opencode.json config
  • Amp / Claude Desktop - claude_desktop_config.json config
  • Cursor - Uses OpenCode config format
  • Claude Code - Uses OpenCode config format

Supported Frameworks

FrameworkRules
Next.jsServer/Client boundaries, data fetching, image optimization
ReactHooks rules, performance, key props
Vue 3Composition API, reactivity, v-for keys
TypeScriptStrict mode, no-any, null checks
DjangoN+1 queries, security, migrations
ExpressAsync errors, security middleware, input validation

Installation Scope

  • Project (recommended) - Installs to ./.opencode/skills/code-reviewer/
  • Global - Installs to ~/.config/opencode/skills/code-reviewer/

Generated Files

.opencode/
├── opencode.json           # MCP server config
├── code-reviewer.json      # Review settings
└── skills/
    └── code-reviewer/
        ├── SKILL.md        # Skill instructions
        └── references/
            ├── security-patterns.md
            ├── performance-patterns.md
            ├── quality-patterns.md
            └── framework-rules/
                ├── nextjs.md
                ├── react.md
                ├── vue.md
                ├── typescript.md
                ├── django.md
                └── express.md

Usage After Installation

# Review a file
opencode "review src/auth.ts"

# Review a directory
opencode "review src/services/"

# Use slash command
/code-reviewer src/

# Review staged changes
/code-reviewer --staged

Rule Priority

Rules are applied in this order (highest to lowest priority):

  • AI Instructions - AGENTS.md, CLAUDE.md, .cursorrules
  • Custom rules - User-defined in code-reviewer.json
  • Linting rules - ESLint, Biome, Prettier
  • Framework rules - Next.js, React, Vue, etc.
  • Built-in rules - Security, performance, quality patterns

MCP Server Integration

The installer configures MCP servers for enhanced code review:

ServerPurposeConfig
GitHubPR reviews, issuesnpx @anthropic/mcp-server-github
GitLabMR reviews, issuesnpx @anthropic/mcp-server-gitlab
LinearIssue trackingHTTP: https://mcp.linear.app/mcp
JiraIssue trackingnpx @anthropic/mcp-server-jira

Tokens are stored in .env (gitignored) and referenced via ${env.TOKEN_NAME}.

Configuration

code-reviewer.json

{
  "version": "1.0.0",
  "project": {
    "detected": {
      "packageManager": "pnpm",
      "language": "typescript",
      "framework": "nextjs",
      "styling": ["tailwind"],
      "linting": ["eslint", "prettier"]
    }
  },
  "rules": {
    "framework": {
      "nextjs": { "enabled": true }
    },
    "language": {
      "typescript": { "enabled": true, "strict": true }
    },
    "builtin": {
      "security": { "enabled": true },
      "performance": { "enabled": true }
    },
    "custom": []
  }
}

Custom Rules

Add custom rules to code-reviewer.json:

{
  "rules": {
    "custom": [
      {
        "name": "no-console-log",
        "severity": "warning",
        "pattern": "console.log",
        "message": "Remove console.log before merging"
      }
    ]
  }
}

Development

# Clone and install
cd packages/create-code-reviewer
npm install

# Build
npm run build

# Test locally
node dist/index.js

License

MIT

Keywords

code-review

FAQs

Package last updated on 05 Feb 2026

Related posts