code-review

Inspect ahead-of-base diffs and generate structured P0-P4 markdown review reports.

325|28|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/SandAI-org/MagiCompiler --skill code-review-sandai-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/SandAI-org/MagiCompiler/tree/main/.cursor/skills/code-review
Command: npx skills add https://github.com/SandAI-org/MagiCompiler --skill code-review-sandai-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

Reviewers spend time on ad-hoc checks; this skill ensures a strict, structured assessment of changes ahead of the base.

Core Features & Use Cases

  • Inspect only ahead-of-base diffs for PRs and local branches.
  • Produce a standardized P0-P4 review structure and render a markdown report.
  • Save and summarize findings within the repository for traceability and collaboration.

Quick Start

To start, ask the skill to review the current branch against its base and generate a structured P0-P4 review.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate a code review for a pull request diff?

To automate code review for a pull request diff, you can use the code-review skill to inspect ahead-of-base changes and generate a structured markdown report. It relies on git for diff computation and the GitHub CLI to fetch PR metadata.

Can I review local branch changes before merging without creating a pull request?

Yes, you can review local branch changes before merging without a pull request by inspecting the ahead-of-base diff. The code-review skill applies to local branches and focuses strictly on changes that will merge.

What is the P0-P4 severity framework in code quality assurance?

The P0-P4 severity framework in code quality assurance is a standardized structure used to categorize review findings. The code-review skill applies this framework to render a rigorous markdown report for pull request diffs.

Does the code-review skill require the GitHub CLI to work?

Yes, the code-review skill requires the GitHub CLI (gh) to work. It depends on gh to fetch pull request metadata, while using git to compute the actual ahead-of-base diffs for review.

How do I save code review findings for pull requests within my repository?

To save code review findings for pull requests within your repository, the code-review skill summarizes and stores the structured P0-P4 markdown report directly inside the repo, ensuring traceability and collaboration.