skills/code-review/SKILL.md
Code Review Plugin
npx skillsauth add kennyolofsson23-netizen/claude-code-config code-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Comprehensive multi-agent code review system that examines code from multiple specialized perspectives to catch bugs, security issues, and quality problems before they reach production.
The Code Review plugin implements a multi-agent code review system where specialized AI agents examine code from different perspectives. Six agents work in parallel: Bug Hunter, Security Auditor, Test Coverage Reviewer, Code Quality Reviewer, Contracts Reviewer, and Historical Context Reviewer. This provides comprehensive, professional-grade code review before commits or pull requests.
# Install the plugin
/plugin install code-review@NeoLabHQ/context-engineering-kit
# Review uncommitted local changes
> /code-review:review-local-changes
# Review a pull request
> /code-review:review-pr #123
Usage Examples
Code Review Command
│
├──> Bug Hunter (parallel)
├──> Security Auditor (parallel)
├──> Test Coverage Reviewer (parallel)
├──> Code Quality Reviewer (parallel)
├──> Contracts Reviewer (parallel)
└──> Historical Context Reviewer (parallel)
│
▼
Aggregated Report
Focus: Identifies potential bugs and edge cases through root cause analysis
What it catches:
Focus: Security vulnerabilities and attack vectors
What it catches:
Focus: Test quality and coverage
What it evaluates:
Focus: Code structure and maintainability
What it evaluates:
Focus: API contracts and interfaces
What it reviews:
Focus: Changes relative to codebase history
What it analyzes:
You can use anthropics/claude-code-action to run this plugin for PR reviews in github actions.
/install-github-app command to setup workflow and secrets..github/workflows/claude-code-review.yml to the following:name: Claude Code Review
on:
pull_request:
types:
- opened
- synchronize # remove if want to run only, when PR is opened
- ready_for_review
- reopened
# Uncomment to limit which files can trigger the workflow
# paths:
# - "**/*.ts"
# - "**/*.tsx"
# - "**/*.js"
# - "**/*.jsx"
# - "**/*.py"
# - "**/*.sql"
# - "**/*.SQL"
# - "**/*.sh"
jobs:
claude-review:
name: Claude Code Review
runs-on: ubuntu-latest
permissions:
contents: read
pull-requests: read
issues: write
id-token: write
actions: read
steps:
- name: Checkout repository
uses: actions/checkout@v4
with:
fetch-depth: 1
- name: Run Claude Code Review
id: claude-review
uses: anthropics/claude-code-action@v1
with:
claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
track_progress: true # attach tracking comment
use_sticky_comment: true
plugin_marketplaces: https://github.com/NeoLabHQ/context-engineering-kit.git
plugins: "code-review@context-engineering-kit\ngit@context-engineering-kit\ntdd@context-engineering-kit\nsadd@context-engineering-kit\nddd@context-engineering-kit\nsdd@context-engineering-kit\nkaizen@context-engineering-kit"
prompt: '/code-review:review-pr ${{ github.repository }}/pull/${{ github.event.pull_request.number }} Note: The PR branch is already checked out in the current working directory.'
# Skill and Bash(gh pr comment:*) is required for review, the rest is optional, but recommended for better context and quality of the review.
claude_args: '--allowed-tools "Skill,Bash,Glob,Grep,Read,Task,mcp__github_inline_comment__create_inline_comment,Bash(gh issue view:*),Bash(gh search:*),Bash(gh issue list:*),Bash(gh pr comment:*),Bash(gh pr edit:*),Bash(gh pr diff:*),Bash(gh pr view:*),Bash(gh pr list:*),Bash(gh api:*)"'
review-local-changes)Produces a structured report organized by severity:
# Code Review Report
## Executive Summary
[Overview of changes and quality assessment]
## Critical Issues (Must Fix)
- [Issue with location and suggested fix]
## High Priority (Should Fix)
- [Issue with location and suggested fix]
## Medium Priority (Consider Fixing)
- [Issue with location]
## Low Priority (Nice to Have)
- [Issue with location]
## Action Items
- [ ] Critical action 1
- [ ] High priority action 1
review-pr)Posts inline comments directly on PR lines - no overall report. Each comment follows this format:
🔴/🟠/🟡 [Critical/High/Medium]: [Brief description]
[Evidence: What was observed and consequence if unfixed]
```suggestion
[code fix if applicable]
development
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
testing
Full QA pass: run all tests, check types, catch regressions, write missing tests. Use when the user says "run tests", "QA", "verify changes", "check for regressions", "test everything", or "make sure it works".
development
Provides guidance for property-based testing across multiple languages and smart contracts. Use when writing tests, reviewing code with serialization/validation/parsing patterns, designing features, or when property-based testing would provide stronger coverage than example-based tests.
development
Initialize a new project with Kenny's universal conventions and stack-appropriate infrastructure. Use this skill whenever: setting up a new project, creating a new repo, scaffolding a new app, starting fresh on a new idea, 'init project', 'new project', 'set up a new app', 'create a project for X', or any variant of starting a new codebase from scratch. Also trigger when the user says 'bootstrap', 'scaffold', or 'kickstart'. This skill ensures every project gets the same quality gates and conventions while adapting infrastructure to the chosen stack.