review

Review code changes between a fixed point and HEAD against repository standards and spec.

16|Updated Jun 6, 2026

Search Tags:#automation #standards #review #diff #spec #code-quality

Ready to run

npx skills add https://github.com/Insik-Han/han-monorepo-template --skill review-insik-han

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Insik-Han/han-monorepo-template/tree/main/.agents/skills/review
Command: npx skills add https://github.com/Insik-Han/han-monorepo-template --skill review-insik-han

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Two-axis review of code changes between a fixed point and HEAD to verify compliance with repository standards and alignment with the originating spec.

Core Features & Use Cases

Pin the fixed point and generate a diff against HEAD to focus reviews on relevant changes.
Run Standards and Spec sub-agents in parallel to produce side-by-side findings.
Produce an aggregate report that helps decide whether to merge, modify, or revert changes.

Quick Start

Provide the fixed point (commit, branch, or tag) to review and run the review workflow to generate both Standards and Spec reports.

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 diff compliance against repository standards and specs?▼

Automated code review analyzes diffs between a fixed point and HEAD to assess compliance with repository standards and alignment with the originating spec. It runs both analyses in parallel to surface findings side-by-side.

Can I review code changes against both standards and original spec at the same time?▼

Yes, parallel two-axis code review runs Standards and Spec sub-agents simultaneously. This generates side-by-side findings that help you evaluate code changes for both repository standards and spec alignment at a glance.

What do I need to run an automated review of my code diff against repository standards?▼

You need a fixed point like a commit, branch, or tag to generate a diff against HEAD. Your repository must also contain standard documents and an issue-tracker workflow to locate the spec and enforce gating rules.

How do I generate a code review report to decide whether to merge or revert changes?▼

Provide a fixed point to generate a diff against HEAD and run the review workflow. The workflow produces an aggregate report from parallel Standards and Spec findings to help you decide whether to merge, modify, or revert changes.

Does automated code review work without an issue-tracker workflow in the repository?▼

No, the review workflow requires access to an issue-tracker workflow to locate the originating spec and enforce gating rules. Standard documents within the repository are also necessary to assess code compliance.

What is two-axis code review and when do I need it for my repository?▼

Two-axis code review verifies code changes against repository standards and spec alignment simultaneously. You need it when evaluating diffs between a fixed point and HEAD to ensure changes meet both quality standards and original requirements.