review

Review code diffs against constitution and acceptance criteria.

5|1|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/joshsmithxrm/power-platform-developer-suite --skill review-joshsmithxrm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/joshsmithxrm/power-platform-developer-suite/tree/main/.claude/skills/review
Command: npx skills add https://github.com/joshsmithxrm/power-platform-developer-suite --skill review-joshsmithxrm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bias-isolated code review ensures reviewers see only the diff, the constitution, and the spec acceptance criteria, never the implementation plan or task context, reducing bias and improving code quality.

Core Features & Use Cases

  • Impartial diff-only reviews visible to reviewers
  • Load constitution from specs/CONSTITUTION.md and apply relevant acceptance criteria
  • Automated review workflow that uses per-file chunks and aggregates QA findings
  • Cross-file consistency checks and a final consolidated report

Quick Start

Provide an impartial code review by submitting the diff and related materials to the review agent, with no plan, task descriptions, or implementation context.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform an impartial code review using only diffs?

To perform an impartial code review, submit the diff, constitution, and spec acceptance criteria while omitting all implementation context. Analyzing only diffs reduces bias and improves code quality.

What is bias-isolated code review and when do I need it?

Bias-isolated code review is the process of evaluating diffs without implementation plans or task context. You need it to prevent prior knowledge from skewing your assessment of code quality and spec compliance.

How do I automate QA findings integration into a code review?

Automate QA findings integration by processing per-file diff chunks and aggregating them with QA results. The workflow applies acceptance criteria and outputs a structured report with actionable findings.

Can I use constitution and spec acceptance criteria to enforce code review rules?

Yes, you can load a constitution from specs/CONSTITUTION.md and apply relevant acceptance criteria. The review enforces these rules across per-file diffs and reports critical and important issues.

Does diff-only code review work without implementation context?

Yes, diff-only code review works by strictly analyzing per-file diffs without any implementation plan. It applies cross-file consistency checks and outputs a final consolidated report.

What are the limitations of bias-isolated code review?

A limitation of bias-isolated code review is that it ignores implementation context and task descriptions entirely. It relies strictly on diffs, constitution, and spec acceptance criteria to generate findings.