Skip to content
alyn
foryourhealth111-pixel

Code Reviewer skill

Default code-quality route for broad code review, PR review, maintainability, correctness, and regression-risk checks. Do not use as the primary route for dedicated OWASP/security audits, review-feedback handling, completion verification, AI-code cleanup, or TDD/test-first work.

$npx skills add foryourhealth111-pixel/Vibe-Skills --skill code-reviewer
View this skill on GitHubforyourhealth111-pixel/Vibe-Skills/bundled/skills/code-reviewer/SKILL.md
Pack stars
3,813
Pack installs
950
Alyn Score
63/99
Updated
2 days ago
License
Apache-2.0
– views – installs via Alyn

Install Code Reviewer

Pick your agent. Every command is ready to paste.

$npx skills add foryourhealth111-pixel/Vibe-Skills --skill code-reviewer

The open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.

01

Install it

Run the command above, or upload the folder in Claude.

02

Ask naturally

Describe the task. Your agent loads code-reviewer when the request matches its description.

03

Name it if needed

If it does not trigger, say “use the code-reviewer skill”. In Codex, type $code-reviewer.

The skill itself

SKILL.md

FolderGitHub

Code Reviewer

Complete toolkit for code reviewer with modern tools and best practices.

Routing Boundary

Use code-reviewer when the user asks for a fresh review of code or a PR:

  • correctness and likely bugs
  • maintainability and readability
  • regression risk
  • test coverage gaps from a reviewer's point of view

Do not let this skill own narrower problems:

  • security-reviewer owns OWASP, secret leak, auth bypass, injection, and dedicated security audit prompts.
  • receiving-code-review owns existing CodeRabbit/GitHub/human review comments.
  • verification-before-completion owns final evidence before claiming work is done.
  • deslop owns cleanup of AI-generated comments, redundant guards, and boilerplate.
  • tdd-guide owns test-first or RED -> GREEN -> REFACTOR development.

Migrated Legacy Assets

The legacy review wrapper has been absorbed into this direct route owner.

  • references/python-style-guide.md contains the retained Python naming, import, documentation, error-handling, and secret-handling guidance.
  • scripts/check_style.py is a lightweight stdin/string style checker for quick local review support.

Use these assets as supporting material inside code-reviewer; do not route to the deleted wrapper skill.

Quick Start

Main Capabilities

This skill provides three core capabilities through automated scripts:

# Script 1: Pr Analyzer
python scripts/pr_analyzer.py [options]

# Script 2: Code Quality Checker
python scripts/code_quality_checker.py [options]

# Script 3: Review Report Generator
python scripts/review_report_generator.py [options]

Core Capabilities

1. Pr Analyzer

Automated tool for pr analyzer tasks.

Features:

  • Automated scaffolding
  • Best practices built-in
  • Configurable templates
  • Quality checks

Usage:

python scripts/pr_analyzer.py <project-path> [options]

2. Code Quality Checker

Comprehensive analysis and optimization tool.

Features:

  • Deep analysis
  • Performance metrics
  • Recommendations
  • Automated fixes

Usage:

python scripts/code_quality_checker.py <target-path> [--verbose]

3. Review Report Generator

Advanced tooling for specialized tasks.

Features:

  • Expert-level automation
  • Custom configurations
  • Integration ready
  • Production-grade output

Usage:

python scripts/review_report_generator.py [arguments] [options]

Reference Documentation

Code Review Checklist

Comprehensive guide available in references/code_review_checklist.md:

  • Detailed patterns and practices
  • Code examples
  • Best practices
  • Anti-patterns to avoid
  • Real-world scenarios

Coding Standards

Complete workflow documentation in references/coding_standards.md:

  • Step-by-step processes
  • Optimization strategies
  • Tool integrations
  • Performance tuning
  • Troubleshooting guide

Common Antipatterns

Technical reference guide in references/common_antipatterns.md:

  • Technology stack details
  • Configuration examples
  • Integration patterns
  • Security considerations
  • Scalability guidelines

Tech Stack

Languages: TypeScript, JavaScript, Python, Go, Swift, Kotlin Frontend: React, Next.js, React Native, Flutter Backend: Node.js, Express, GraphQL, REST APIs Database: PostgreSQL, Prisma, NeonDB, Supabase DevOps: Docker, Kubernetes, Terraform, GitHub Actions, CircleCI Cloud: AWS, GCP, Azure

Development Workflow

1. Setup and Configuration

# Install dependencies
npm install
# or
pip install -r requirements.txt

# Configure environment
cp .env.example .env

2. Run Quality Checks

# Use the analyzer script
python scripts/code_quality_checker.py .

# Review recommendations
# Apply fixes

3. Implement Best Practices

Follow the patterns and practices documented in:

  • references/code_review_checklist.md
  • references/coding_standards.md
  • references/common_antipatterns.md

Best Practices Summary

Code Quality

  • Follow established patterns
  • Write comprehensive tests
  • Document decisions
  • Review regularly

Performance

  • Measure before optimizing
  • Use appropriate caching
  • Optimize critical paths
  • Monitor in production

Security

  • Flag obvious security risks during a general review.
  • Route dedicated OWASP, auth, secret, injection, or threat-model requests to security-reviewer.

Maintainability

  • Write clear code
  • Use consistent naming
  • Add helpful comments
  • Keep it simple

Common Commands

# Development
npm run dev
npm run build
npm run test
npm run lint

# Analysis
python scripts/code_quality_checker.py .
python scripts/review_report_generator.py --analyze

# Deployment
docker build -t app:latest .
docker-compose up -d
kubectl apply -f k8s/

Troubleshooting

Common Issues

Check the comprehensive troubleshooting section in references/common_antipatterns.md.

Getting Help

  • Review reference documentation
  • Check script output messages
  • Consult tech stack documentation
  • Review error logs

Resources

  • Pattern Reference: references/code_review_checklist.md
  • Workflow Guide: references/coding_standards.md
  • Technical Guide: references/common_antipatterns.md
  • Tool Scripts: scripts/ directory

Tips for Code Reviewer

  • • Start a fresh session after installing so your agent picks up the new skill.
  • • This skill ships scripts. Read them before the first run, and run it in a project without secrets first.
  • • It bundles reference files. The agent reads them only when needed, so they cost no context until then.
  • • It is part of a pack with 30 skills. Install only the ones you need with --skill to keep triggers precise.
  • • If two skills overlap, mention the one you want by name.

Questions about Code Reviewer

What does the Code Reviewer skill do?

Default code-quality route for broad code review, PR review, maintainability, correctness, and regression-risk checks. Do not use as the primary route for dedicated OWASP/security audits, review-feedback handling, completion verification, AI-code cleanup, or TDD/test-first work.

How do I install Code Reviewer?

Run "npx skills add foryourhealth111-pixel/Vibe-Skills --skill code-reviewer" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.

Does Code Reviewer work in Cursor and Codex?

Yes. Code Reviewer uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.

Is Code Reviewer free?

Code Reviewer is open source on GitHub under the Apache-2.0 license. It is free to install; check the license before commercial use.

Who made Code Reviewer?

Code Reviewer is published by foryourhealth111-pixel in the foryourhealth111-pixel/Vibe-Skills repository, together with 29 other skills.

Similar skills. From other creators.