code-review-review

Identify code defects using design-intent, PR body, and git diff evidence.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/KangJiSseok/ACODIAN --skill code-review-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-review
Source: https://github.com/KangJiSseok/ACODIAN/tree/main/.codex/skills/code-review-review
Command: npx skills add https://github.com/KangJiSseok/ACODIAN --skill code-review-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates rigorous, evidence-based code reviews by anchoring feedback to explicit design intent, PR body context, and the actual code changes, reducing subjective comments and rework.

Core Features & Use Cases

  • Evidence-based evaluation against design intent
  • Contextual review of PR body and git diff
  • Prioritized feedback aligned with ADR/GEN references (p1–p4)
  • Generated review artifacts for traceability

Quick Start

Submit input artifacts and trigger the reviewer to produce structured, evidence-based comments.

Frequently Asked Questions about code-review-review

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

FAQPage Schema
How do I automate evidence-based code review for pull requests?

Evidence-based code review is automated by anchoring feedback to design intent, PR body context, and git diff. This approach identifies defects using explicit ADR references and code-quality guidelines to produce prioritized, structured comments.

What is evidence-based code review and how does it use design intent?

Evidence-based code review evaluates code changes against explicit design intent and ADR documentation. It reduces subjective comments by cross-referencing the PR body and git diff with established architectural guidelines to find actual defects.

How do I structure code review comments with ADR and prioritized feedback?

Code review comments are structured by aligning findings with ADR and GEN items, then assigning priority levels from p1 to p4. This generates traceable review artifacts based on the git diff and design intent.

Can I use automated code review for feature branches requiring rigorous evaluation?

Automated code review applies directly to feature branches requiring rigorous evaluation. It processes the full code changes across the branch, using PR body context and design intent to ensure evidence-based defect detection.

What are the limitations of design-intent based code review?

Design-intent based code review requires explicit ADR documentation and a descriptive PR body to function effectively. Without these inputs, the tool cannot ground its findings or map defects back to architectural guidelines.