kiro-review

Review task implementations against specifications and output verdicts with remediation steps.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/BarryYin/Hermes-sdd --skill kiro-review-barryyin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-review
Source: https://github.com/BarryYin/Hermes-sdd/tree/main/skills/kiro-review
Command: npx skills add https://github.com/BarryYin/Hermes-sdd --skill kiro-review-barryyin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that completed task implementations truly satisfy approved requirements and design commitments while staying within declared task boundaries, preventing scope drift and hidden coupling.

Core Features & Use Cases

  • Mechanical verification: Run tests and targeted static checks, scan diffs for placeholders and secrets, and report concrete pass/fail signals.
  • Boundary and design alignment: Compare code changes to task Boundary: constraints, referenced requirements sections, and design commitments to detect spillover or hidden dependencies.
  • Decision output: Produce a clear APPROVED or REJECTED verdict with findings, severity, and mandatory remediation steps for reviewers and integrators.

Quick Start

Ask the skill to review task TASK-123 with the spec file paths, the implementer's status report, and the git diff to produce an APPROVED or REJECTED verdict and remediation if needed.

Frequently Asked Questions about kiro-review

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

FAQPage Schema
How do I verify task implementations against approved specifications before merging?

To verify task implementations against approved specifications, compare code changes to task boundary constraints and referenced requirements, run tests and static checks, and scan diffs for placeholders to produce an APPROVED or REJECTED verdict.

What is spec-driven code review and how does it prevent scope drift?

Spec-driven code review validates completed implementations against approved requirements and design commitments, detecting spillover and hidden dependencies to prevent scope drift while ensuring declared task boundaries are respected.

How do I automate pre-merge validation when an implementer marks a task READY_FOR_REVIEW?

Automate pre-merge validation by running mechanical tests, executing targeted static analysis, scanning diffs for secrets, and comparing changes against task boundaries to generate a concise verdict with remediation steps.

Can I use static analysis to scan diffs for placeholders and secrets during code review?

Yes, static analysis scans diffs during code review to detect placeholders and secrets, reporting concrete pass or fail signals alongside boundary and design alignment checks for spec-driven validation.

What's the best way to check for hidden coupling and boundary spillover in a code diff?

The best way to check for hidden coupling and boundary spillover is comparing code changes against declared task boundary constraints and design commitments, identifying dependencies that exceed the approved specification scope.

Why does my task acceptance check fail even when tests pass?

Task acceptance checks fail even when tests pass if the diff contains placeholders, secrets, or changes exceeding declared task boundaries, triggering a REJECTED verdict with mandatory remediation steps.