kiro-review

Review task implementations against approved specs and verification evidence.

2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/snicmakino/kolt --skill kiro-review-snicmakino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-review
Source: https://github.com/snicmakino/kolt/tree/main/.claude/skills/kiro-review
Command: npx skills add https://github.com/snicmakino/kolt --skill kiro-review-snicmakino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review and validate that a task implementation adheres to approved requirements, boundary commitments, and supporting verification evidence.

Core Features & Use Cases

  • Boundary alignment: checks that changes stay within the defined task scope and do not introduce hidden cross-boundary couplings.
  • Mechanical verification: analyzes diffs against requirements/design and corroborates with tests and status reports.
  • Decision outputs: returns a clear APPPROVED or REJECTED verdict with actionable remediation and a concise summary.

Quick Start

Run kiro-review with the task ID and relevant artifacts to obtain an official verdict and findings.

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 implementation adheres to approved specs and boundaries?

To verify task implementation adheres to approved specs, you can run an automated review against the project diff, tests, and documentation to produce a binary verdict. The review checks boundary alignment and enforces mechanical verification.

When do I need to run a pre-acceptance code review for spec compliance?

Pre-acceptance code review is needed after a task is implemented or remediated to validate mechanical checks and evidence-driven assessment. It ensures the code respects committed boundaries before final approval using project diffs and test results.

How do I check code changes for cross-boundary couplings and scope creep?

Checking code changes for cross-boundary couplings involves analyzing the task diff to ensure modifications stay within the defined task scope. The review validates that no hidden dependencies or out-of-scope alterations were introduced during implementation.

Does mechanical code review produce a binary approved or rejected verdict?

Yes, mechanical code review produces a clear APPPROVED or REJECTED verdict based on evidence-driven assessment. Alongside the binary verdict, it provides actionable remediation steps and a concise summary of the findings.

What is the best way to audit task work against verification evidence and requirements?

The best way to audit task work is to run an automated review that coroborates diffs with tests and status reports against the approved design. This evidence-driven assessment validates requirements compliance and identifies any boundary violations.