code-review

Analyze diffs and artifacts to verify implementation against the approved contract.

3|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/xiongxianfei/rigorloop --skill code-review-xiongxianfei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/xiongxianfei/rigorloop/tree/main/.codex/skills/code-review
Command: npx skills add https://github.com/xiongxianfei/rigorloop --skill code-review-xiongxianfei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams verify that code changes satisfy the approved contract, spec, and validation artifacts before merging, reducing risk and misalignment.

Core Features & Use Cases

  • Independent review against the contract: compare diffs, plans, architecture docs, and test results to ensure alignment.
  • Workflow gate support: used during PR readiness, QA validation, and release checks to confirm coverage of requirements.
  • Evidence-backed conclusions: outputs a structured first-pass review with findings, risks, and recommended actions.

Quick Start

Provide the actual diff and supporting artifacts to the reviewer and run an independent-review pass.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I verify code changes satisfy the approved spec and architecture before merging?

To verify code changes satisfy the approved spec, you analyze the actual diff against tracked artifacts like plans, architecture docs, and ADRs. This independent review process outputs a structured record with findings, risks, and recommended actions to ensure alignment.

What is an independent review pass for PR readiness?

An independent review pass for PR readiness compares diffs and test results against the approved contract to confirm coverage of requirements. It acts as a workflow gate to ensure implementation aligns with the spec, architecture, and plan before merging.

How do I validate diff alignment with ADRs and test results?

You validate diff alignment by providing the actual diff and supporting artifacts like ADRs and test results to run an independent-review pass. This assesses implementation alignment with the spec, architecture, and plan, generating a first-pass review record with risks and actions.

Do I need tracked artifacts like architecture docs and plans for code review?

Yes, you need tracked artifacts like architecture docs, plans, ADRs, and test results for code review. These supporting artifacts are required to compare against the actual diff and verify that the implementation satisfies the approved contract.

What's the best way to structure code review findings and recommended actions?

The best way to structure code review findings is through an evidence-backed first-pass review record. This record outputs structured findings, risks, and recommended actions based on comparing diffs, plans, architecture docs, and test results to confirm spec compliance.