code-reviewer

Automate code review of git diffs to detect correctness issues and guideline violations.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/bcmcpher/my-skills --skill code-reviewer-bcmcpher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/bcmcpher/my-skills/tree/main/plugins/programming-tools/agents/code-reviewer
Command: npx skills add https://github.com/bcmcpher/my-skills --skill code-reviewer-bcmcpher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the code review process to detect correctness issues, project-guideline violations, and quality risks in code changes, helping teams ship reliable software faster.

Core Features & Use Cases

  • Automatic review of unstaged or staged changes from git diff to surface defects and policy violations.
  • Enforces project rules and best practices, including import conventions, naming patterns, and testing requirements.
  • Use Case: Before creating a pull request, run the reviewer to generate a concise issue report with recommended fixes.

Quick Start

Activate the code-reviewer agent on your current Git workspace to review unstaged changes.

Frequently Asked Questions about code-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review for a git diff before creating a pull request?

Automate code review by analyzing unstaged or staged git diffs to detect correctness issues and policy violations. This generates a structured issue report with recommended fixes, ensuring quality before opening a pull request.

What is static analysis for pull requests and how does it enforce project guidelines?

Static analysis for pull requests applies rule-based checks to code changes to enforce project guidelines. It detects violations in import conventions, naming patterns, and testing requirements, providing structured issue scoring and remediation guidance.

Does automated code review work with local changes across different programming languages?

Automated code review works across languages and repositories by evaluating local unstaged or staged changes. It targets user-specified file sets or git diffs to identify quality risks and defects regardless of the programming language.

Can I use rule-based analysis to surface defects in specific file sets?

Rule-based analysis can target user-specified file sets to surface defects and quality risks. By focusing the review on specific changes rather than the entire repository, it delivers concise issue reports with clear remediation guidance.

What are the limitations of using automated review automation for quality assurance?

Review automation relies on diff-based input and rule-based analysis, meaning it evaluates changes rather than entire codebases. It focuses on correctness issues and guideline violations, providing structured issue scoring rather than executing runtime tests.