review

Assess code adherence to standards and PRD specifications using Git diff.

4|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/hwj123hwj/custom-skills --skill review-hwj123hwj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/hwj123hwj/custom-skills/tree/main/skills/review
Command: npx skills add https://github.com/hwj123hwj/custom-skills --skill review-hwj123hwj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, issue tracker, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of code review, ensuring both adherence to coding standards and implementation accuracy by simultaneously assessing both standards and specification.

Core Features & Use Cases

  • Two-axis Review: Evaluates both Standards (adherence to coding standards) and Spec (implementation against the originating issue/PRD) simultaneously.
  • Parallel Sub-agents: Keeps the context of each review separate to avoid interference.
  • Integration with Issue Trackers: Fetches originating issues/PRDs for spec review if the project uses an issue tracker.
  • Use Case: Ideal for reviewing a branch, a PR, or work-in-progress changes to ensure that code aligns with the intended design and follows established standards.

Quick Start

To review a branch against the last stable commit, use the following command: npx custom-skills run review -- <branch-name>.

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 to check both PRD adherence and coding standards?

Automated code review checks PRD adherence and coding standards by fetching originating issues and evaluating Git diffs in parallel. This dual-axis approach isolates spec compliance from standards checks to prevent context interference.

What is two-axis code review and how does it work with Git diffs?

Two-axis code review evaluates implementation correctness against originating PRDs and adherence to documented coding standards. It processes Git diffs through parallel sub-agents, keeping each review context isolated to avoid interference.

Do I need an issue tracker to review code against design specifications?

You need an issue tracker to fetch originating PRDs and issues for spec review. Git is also required to access repository diffs, ensuring the code review accurately assesses implementation against design specifications.

How can I review a branch against the last stable commit?

Review a branch against the last stable commit by running the review command with the branch name. This triggers parallel sub-agents to assess Git diffs for both standards adherence and spec compliance.

Best way to ensure work-in-progress code aligns with intended design specifications?

Ensure work-in-progress code aligns with design specifications by running a two-axis code review. It fetches the originating PRD from your issue tracker and evaluates the Git diff to verify implementation accuracy.

Can I review a pull request for both implementation accuracy and standards compliance?

You can review a pull request for implementation accuracy and standards compliance simultaneously. The parallel processing mechanism fetches issue context and evaluates Git diffs to ensure both spec adherence and coding standards.