review-code

Review branch or PR diffs for quality, correctness, security, and standards.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/daddia/space --skill review-code-daddia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/daddia/space/tree/main/.agents/skills/review-code
Command: npx skills add https://github.com/daddia/space --skill review-code-daddia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performs a code-review for changes in a branch or PR to ensure quality, correctness, security, and adherence to project standards before merge.

Core Features & Use Cases

  • Automated diff analysis for quality, correctness, security, and standards compliance.
  • Structured verdict generation with actionable findings for developers, reviewers, and maintainers.
  • Use Case: When a PR introduces changes, analyze the diff and flag regressions, design mismatches, or potential issues.

Quick Start

Review the changes in the provided branch or PR and return a structured verdict.

Frequently Asked Questions about review-code

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

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

Automating code review for a pull request involves analyzing branch diffs to enforce quality, correctness, and security standards before merging. It flags regressions and generates a structured verdict with actionable findings for maintainers.

What does a structured code review verdict include for CI/CD workflows?

A structured code review verdict includes actionable findings regarding security checks, error handling, and test coverage. It verifies acceptance criteria against project standards, ensuring the branch meets merge requirements in CI/CD workflows.

Can I verify acceptance criteria and test coverage during diff analysis?

Yes, diff analysis can verify acceptance criteria against project standards like a backlog and check test coverage. It evaluates code changes to ensure they fulfill requirements and handle errors correctly before outputting a structured verdict.

How do I check branch changes for security and best practices before merge?

Checking branch changes involves applying automated diff analysis to scan for security vulnerabilities and enforce best practices. This verifies code matches project standards and returns a structured verdict to guide the merge decision.

What is the best way to flag regressions and design mismatches in a PR?

The best way to flag regressions and design mismatches in a PR is to perform thorough diff analysis against project standards. This identifies potential issues early and outputs a structured verdict detailing actionable findings for developers.