skills.rest
sacharavya
sacharavyaCOMMUNITY
Explore all skills by this author →
GitHub

code-reviewer

Identify and report logic bugs, style issues, naming problems, and complexity in code.

Updated Aug 27, 2026
Search Tags:#maintainability#code-quality#static-analysis#code-review#diff-review#language-agnostic
One-click install
npx skills add https://github.com/sacharavya/b-b-i-crm --skill code-reviewer-sacharavya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/sacharavya/b-b-i-crm/tree/main/.claude/skills/code-reviewer
Command: npx skills add https://github.com/sacharavya/b-b-i-crm --skill code-reviewer-sacharavya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews code for logic bugs, style issues, naming problems, complexity, and anti-patterns. Produces structured feedback with severity levels to guide fixes.

Core Features & Use Cases

  • Structured, severity-ranked feedback across any programming language
  • Review can target a single function, an entire file, or a diff from a PR
  • Real-world use: paste a snippet or PR diff to surface top issues and recommended fixes

Quick Start

Paste the code or diff you want reviewed and specify any language or style guidelines.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I perform a code review on a pull request diff?▼

To perform a code review on a pull request diff, paste the diff into the tool and specify any language or style guidelines. It analyzes the changes to identify and report logic bugs, style issues, and complexity, producing structured, actionable feedback with severity levels to guide fixes.

Can I use static analysis to find logic bugs and complexity in any programming language?▼

Yes, you can use static analysis to find logic bugs and complexity across any programming language. The tool provides language-agnostic analysis, identifying anti-patterns and naming problems in single functions, entire files, or PR diffs while prioritizing issues by severity.

What is the best way to get structured, actionable feedback for code quality issues?▼

The best way to get structured, actionable feedback for code quality issues is to run a review on your code or diff. The tool evaluates maintainability, highlighting naming problems and anti-patterns while ranking findings by severity to clearly guide necessary fixes.

Does language-agnostic code review work for onboarding to new codebases?▼

Yes, language-agnostic code review works for onboarding to new codebases. By analyzing entire files or specific functions, it surfaces top issues, complexity, and anti-patterns, providing severity-based prioritization that helps developers quickly understand code quality and maintainability.

How do I prioritize fixes when reviewing code for maintainability?▼

To prioritize fixes when reviewing code for maintainability, rely on the severity-based prioritization provided in the structured feedback. It evaluates logic bugs, style issues, and complexity, ranking the findings so you can systematically address the most critical code quality problems first.

Related Skills

Explore More Software Engineering Skills→
tygwantygwan
1

quality-gate

Automate quality validation at pre-commit, pre-merge, pre-release, and post-release CI gates.

Community
Advanced
rachel353rachel353

code-review-small

Review small PR diffs for style, naming, and obvious bugs.

Community
Intermediate
samjhechtsamjhecht
4

requesting-code-review

Dispatch a code-review subagent to verify implementation against plan or requirements.

Community
Basic
managedcodemanagedcode
466

dotnet-code-analysis

Configure .NET projects with Roslyn analyzers and .editorconfig rules.

Official
Advanced