code-review

Review code changes and generate severity-rated reports with fix recommendations.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/ssccio/cc-on-web-base --skill code-review-ssccio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/ssccio/cc-on-web-base/tree/main/skills/code-review
Command: npx skills add https://github.com/ssccio/cc-on-web-base --skill code-review-ssccio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents bugs, security vulnerabilities, and maintainability issues from reaching production by providing a structured review before changes are merged.

Core Features & Use Cases

  • Severity-rated findings that clearly distinguish CRITICAL, HIGH, MEDIUM, and LOW issues for faster decision-making.
  • Security, quality, performance, and maintainability coverage using a checklist that maps to common real-world risk areas (e.g., injection, XSS, CSRF, complexity, duplication).
  • Actionable remediation guidance including specific file and line locations plus concrete fix recommendations.

Quick Start

Use the code-review skill to review the changes in your current pull request by asking: "Please run a code review of this diff and return a severity-ranked report with exact file:line locations and fixes."

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I run a security-focused code review on a pull request before merging?

Run a security-focused code review by submitting your pull request diff to identify vulnerabilities, quality issues, and maintainability risks, receiving a severity-ranked report with file:line locations and concrete fixes.

What types of security vulnerabilities and code quality issues can a pre-merge review detect?

A pre-merge review detects security vulnerabilities like injection, XSS, and CSRF, alongside code quality, performance, complexity, and duplication risks, categorizing each finding by severity level for faster decision-making.

How do I get severity-rated findings for my git diff to prioritize bug fixes?

Get severity-rated findings by submitting your git diff for analysis, which returns a categorized report distinguishing CRITICAL, HIGH, MEDIUM, and LOW issues with specific file and line locations plus actionable remediation guidance.

Can I use automated code review for post-feature implementation assessments across modified files?

Yes, you can use automated code review for post-feature implementation assessments across modified files and targeted scopes, producing a comprehensive categorized report with an approval recommendation based on detected risks.

Does pre-merge code review provide actionable remediation guidance for maintainability risks?

Pre-merge code review provides actionable remediation guidance for maintainability risks by mapping findings to a real-world risk checklist and delivering specific file and line locations with concrete fix recommendations.

What is the best way to verify code quality and security in a developer workflow before production?

The best way to verify code quality and security in a developer workflow is applying a structured pre-merge review that prevents bugs and vulnerabilities from reaching production by providing a severity-ranked report with an approval recommendation.