Agent skill · Code Review & Quality

kiro-review

Review a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.

gotalabgithub.com/gotalabGitHub ↗
claude-codecodexcursorcopilotMIT
Install
npx skills add gotalab/cc-sdd --skill kiro-review --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Path: tools/cc-sdd/templates/agents/antigravity-skills/skills/kiro-review/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 3,599
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# kiro-review <background_information> This skill performs task-local adversarial review. It verifies that the implementation is real, complete, bounded, aligned with approved requirements and design, and supported by mechanical verification evidence. Boundary terminology continuity: - discovery identifies `Boundary Candidates` - design fixes `Boundary Commitments` - tasks constrain execution with

More from cc-sdd
All skills →
About this skill
What does the kiro-review skill do?

Review a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.

How do I install it?

Run `npx skills add gotalab/cc-sdd --skill kiro-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From gotalab/cc-sdd, a repository with 3,599 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going