One-click install
npx skills add https://github.com/haryelramalho/skills --skill review-haryelramalho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/haryelramalho/skills/tree/main/skills/community/review
Command: npx skills add https://github.com/haryelramalho/skills --skill review-haryelramalho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you evaluate code changes in a disciplined way by separating implementation quality from requirement fit, so you can catch both style issues and missed intent before merge.

Core Features & Use Cases

  • Two-axis review: Checks changes against documented coding standards and against the originating issue, PRD, or spec.
  • Parallel analysis: Runs independent sub-agents for standards and spec so each review stays focused and unbiased.
  • Branch and PR review: Useful for reviewing a feature branch, pull request, or any work-in-progress diff since a chosen fixed point.
  • Example use case: A developer asks for a review of changes since main, and the Skill returns separate findings for repository conventions and requirement coverage.

Quick Start

Review the changes since main and tell me whether they follow our standards and match the spec.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a pull request against coding standards and spec compliance?

To review a pull request against coding standards and spec compliance, compare HEAD against a resolved base reference and analyze the diff. This separates implementation quality from requirement fit to catch both style issues and missed intent.

What is the best way to evaluate a branch diff for requirement coverage?

Evaluating a branch diff for requirement coverage requires validating the diff against an originating issue, PRD, or spec source. Running independent parallel analysis ensures the requirement fit check stays focused and unbiased.

Can I review work-in-progress code changes against a fixed point?

Yes, you can review work-in-progress code changes against a fixed point by supplying a resolved base reference. This allows the review to analyze the resulting diff separately for both repository conventions and requirement coverage.

How does parallel sub-agent analysis work for code reviews?

Parallel sub-agent analysis for code reviews works by running independent evaluations for coding standards and spec compliance simultaneously. This dual-axis approach ensures each review stays focused and unbiased when checking the diff.

Do I need a base reference and a spec source to review a branch?

Yes, you need a resolved base reference to generate the diff, and an issue, PRD, or spec source to validate requirement fit. Both inputs are required to perform the two-axis branch review.

Why separate coding standards checks from spec compliance during a diff review?

Separating coding standards checks from spec compliance during a diff review catches both style issues and missed intent before merge. Evaluating these two axes independently prevents bias and provides distinct findings.