cc-review

Name: cc-review
Availability: InStock
Author: algforge

Collect Git diffs and evaluate changes against a structured review checklist.

Updated May 7, 2026

Search Tags:#automation #checklist #diff #code-review #pull-request #reviewer

Ready to run

npx skills add https://github.com/lgzarturo/codeconductor --skill cc-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cc-review
Source: https://github.com/lgzarturo/codeconductor/tree/main/.agents/skills/cc-review
Command: npx skills add https://github.com/lgzarturo/codeconductor --skill cc-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run a structured code review — produces a Review Report with CRITICAL, WARNING, and SUGGESTION findings; CRITICAL findings block merge.

Core Features & Use Cases

Diff collection and target specification (branch, file, PR, or working diff)
Automated review against a multi-dimensional checklist (Correctness, Architecture alignment, Security, Performance, Test coverage, Documentation)
Generate a formatted Review Report suitable for developer feedback and merge decisions

Quick Start

Provide a target (branch, file, PR, or diff) to the cc-review workflow and run to produce the Review Report.

Frequently Asked Questions about cc-review

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

FAQPage Schema

How do I run a structured code review on a pull request?▼

Run a structured code review by supplying a pull request, branch, file, or working diff as the target. The process collects the diff, evaluates it against a checklist covering correctness, security, and performance, and outputs a Review Report.

What does an automated code review checklist evaluate?▼

An automated code review checklist evaluates Git diffs across six dimensions: Correctness, Architecture alignment, Security, Performance, Test coverage, and Documentation to identify potential issues before merging.

Can I block unsafe merges automatically using a code review report?▼

You can block unsafe merges using the Review Report. It classifies findings as CRITICAL, WARNING, or SUGGESTION, and CRITICAL findings formally block the merge decision to prevent unsafe code integration.

How do I review a Git diff for security and performance issues?▼

Review a Git diff for security and performance issues by running a structured checklist evaluation against the collected changes. This process systematically identifies vulnerabilities and bottlenecks before producing a summarized Review Report.

Do I need external dependencies to perform an automated code review?▼

No external dependencies are required to perform an automated code review. The workflow operates independently to collect Git diffs, evaluate changes against its checklist, and generate a formatted Review Report for merge decisions.

What is the best way to generate a code review report for developer feedback?▼

Generate a code review report by running an automated evaluation against a Git diff. This produces a formatted document containing CRITICAL, WARNING, and SUGGESTION findings suitable for developer feedback and merge decisions.