review

Analyze Git changes across nine dimensions and generate review artifacts.

6|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/Corvalis-LLC/Crow-Stack --skill review-corvalis-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Corvalis-LLC/Crow-Stack/tree/main/skills/review
Command: npx skills add https://github.com/Corvalis-LLC/Crow-Stack --skill review-corvalis-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code reviews are time-consuming and error-prone. This Skill automates the process by analyzing git changes across multiple dimensions and producing a structured walkthrough, a changes table, and a guided fixes plan.

Core Features & Use Cases

  • Detect changes and prioritize review focus using a nine-dimension analysis (security, logic, duplication, cross-file impact, testing gaps, etc.).
  • Generate an end-to-end review artifact: walkthrough, changes table, and categorized findings.
  • Orchestrate fixes via subagents and load relevant auto-skills to prepare precise, file-level changes.
  • Enable a clean handoff by preparing commits with targeted fixes.

Quick Start

Run /review on your changed files to generate a comprehensive code-review report and automated fixes for your latest changes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for git changes across multiple dimensions?

Automated code review for git changes analyzes diffs across nine dimensions including security, logic, duplication, and testing gaps to generate a structured walkthrough, changes table, and categorized fixes plan. It orchestrates remediation via subagents to prepare precise file-level changes.

What is static analysis for code review and when do I need it?

Static analysis for code review systematically evaluates git diffs to detect security vulnerabilities, logic errors, duplication, cross-file impact, and testing gaps. You need it when manual review becomes time-consuming or error-prone, especially for complex repository changes requiring multi-dimensional assessment.

How do I generate a code review walkthrough and fixes plan from a git diff?

Run an automated review on changed files to generate a comprehensive code-review report including an end-to-end walkthrough, changes table, and categorized findings. The analysis prioritizes focus across nine dimensions and orchestrates fixes via subagents with targeted, file-level changes.

Can I use automated code review for any repository or specific languages only?

Automated code review applies to code changes in any repository regardless of language. It analyzes git changes uniformly across nine dimensions—security, logic, duplication, cross-file impact, testing gaps, and more—producing consistent walkthrough artifacts and fixes plans.

Does automated code review orchestrate fixes or just report findings?

Automated code review orchestrates fixes via subagents and loads relevant auto-skills to prepare precise, file-level changes. Beyond generating a walkthrough and changes table, it enables a clean handoff by preparing commits with targeted fixes for the identified issues.

What are the limitations of automated static analysis for code review?

Automated static analysis focuses on detectable patterns within git diffs across nine dimensions but may not capture nuanced architectural decisions or business logic context. It produces structured findings and fixes plans, but human judgment remains valuable for complex cross-file impact assessment and security trade-offs.