code-review

Identify bugs, security vulnerabilities, and performance issues in code.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Ben2pc/g-claude-code-plugins --skill code-review-ben2pc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Ben2pc/g-claude-code-plugins/tree/main/plugins/example-plugin/skills/code-review
Command: npx skills add https://github.com/Ben2pc/g-claude-code-plugins --skill code-review-ben2pc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often struggle to identify bugs, security vulnerabilities, and performance issues across large codebases during reviews and maintenance. This skill provides structured, repeatable feedback to improve code quality and security.

Core Features & Use Cases

  • Automated code review focusing on bugs, security gaps, and performance bottlenecks.
  • Actionable feedback with concrete recommendations and maintainability notes.
  • Works with multiple languages and integrates into PRs, CI pipelines, and audits for faster quality assurance.

Quick Start

Request a code review of the latest changes to surface defects and improvement opportunities.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I find security vulnerabilities and performance issues during a PR review?

Automated code review identifies security vulnerabilities and performance issues during PR reviews by producing deterministic, actionable feedback with suggested fixes and maintainability notes across multiple languages.

What is the best way to audit a multi-language repository for bugs and maintainability?

Auditing a multi-language repository for bugs requires structured code review that identifies defects across front-end and back-end components, providing actionable maintainability notes to improve codebase quality.

Does static analysis work for both front-end and back-end components in ongoing quality assurance?

Static analysis works for front-end and back-end components during ongoing quality assurance by applying repeatable feedback to identify bugs, security gaps, and performance bottlenecks across multi-language repositories.

Can I integrate automated code review into CI pipelines for faster quality assurance?

Automated code review integrates into CI pipelines for faster quality assurance, enabling continuous detection of bugs, security vulnerabilities, and performance issues across multi-language repositories.

How do I get actionable feedback with suggested fixes for code defects?

Requesting a code review surfaces bugs, security gaps, and performance bottlenecks, producing deterministic actionable feedback with suggested fixes and maintainability notes for identified code defects.

When should I not use automated code review for debugging?

Automated code review should not replace interactive debugging for complex runtime state issues, as it focuses on static analysis to identify deterministic bugs, security vulnerabilities, and performance bottlenecks.