sdlc-review

Verifies Kanban implementation handoffs and routes review verdicts to approve, request changes, or escalate.

1|Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Chia1104/agent-air --skill sdlc-review-chia1104
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdlc-review
Source: https://github.com/Chia1104/agent-air/tree/main/skills/hermes/devops/sdlc-review
Command: npx skills add https://github.com/Chia1104/agent-air --skill sdlc-review-chia1104

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Work handed off from a Kanban implementation lane to the review lane needs an independent verdict before completion, but rubber-stamping handoff summaries or letting reviewers edit the deliverable weakens quality control. This Skill enforces a structured, evidence-based review process with clear verdict routing. ## Core Features & Use Cases - Independent Verification: Reads the task record via kanban_show, inspects the actual deliverable, and runs builds, tests, and lint checks before deciding. - Round-Based Review Lenses: Varies inspection strategy per review round (artifact cold-read, execution-based verification, strict contract audit) to catch different defect classes. - Verdict Routing: Approves with kanban_complete, returns correctable defects with kanban_request_changes, or escalates human decisions with kanban_block, always with concrete evidence. - Use Case: A dispatcher spawns a reviewer for a task in the review lane; the Skill guides the reviewer to map every acceptance criterion to evidence, re-test prior requested changes, and record a single terminal verdict without editing the implementation. ## Quick Start Review the current Kanban task in the review lane by reading its handoff with kanban_show, verifying the deliverable against the acceptance criteria, and submitting an approve, request-changes, or escalate verdict with evidence.

Frequently Asked Questions about sdlc-review

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

FAQPage Schema
How do I review a Kanban task in the review lane?▼

Start with kanban_show to read the task specification, acceptance criteria, and latest review_requested handoff. Then inspect the actual deliverable, run relevant tests or builds, and submit exactly one verdict: approve, request changes, or escalate.

How to request changes on a Kanban implementation handoff?▼

Record actionable findings with kanban_comment stating the defect location, reproduction, and required correction, then call kanban_request_changes with a concise reason. The task returns to its original implementer for rework.

When should a reviewer escalate instead of requesting changes?▼

Escalate with kanban_block only when a human decision or external prerequisite is required and the reviewer and implementer cannot resolve it. Correctable implementation defects belong in kanban_request_changes, not blockers.

What are review lenses in multi-round code review?▼

Review lenses vary the inspection strategy per round: round 1 reads the artifact cold, round 2 executes and tests the work empirically, and round 3+ audits strictly against the original contract. Varied lenses catch different defect classes instead of repeating findings.

Can a reviewer edit the implementation during review?▼

No. The reviewer must preserve role separation and never edit implementation files. Defects are returned to the implementer via kanban_request_changes, and the reviewer independently verifies the next candidate in the following review run.