speckit-review

Review code changes against specifications and update task statuses.

2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-review-pradeepmouli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-review
Source: https://github.com/pradeepmouli/lspeasy/tree/main/.github/skills/speckit-review
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-review-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables engineering teams to perform structured, auditable reviews of completed implementations and keep task statuses in sync with review outcomes.

Core Features & Use Cases

  • Load feature context and specifications to inform a targeted review.
  • Identify the review targets by task ID or review all pending work.
  • Validate changes against acceptance criteria, plan decisions, and documentation, then generate a comprehensive review report.
  • Update tasks.md to reflect completed reviews and decisions.

Quick Start

Run the speckit-review workflow on your feature branch and specify any task IDs to review.

Frequently Asked Questions about speckit-review

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

FAQPage Schema
How do I perform a structured code review against acceptance criteria?

A structured code review validates changes against acceptance criteria, plan decisions, and documentation to generate a comprehensive review report. The process identifies review targets by task ID or pending work, applies structured evaluation, and reports actionable issues.

How do I map code changes to feature specifications during a review?

To map code changes to specifications, load the feature context and specifications to inform a targeted review. The workflow identifies review targets, validates changes against acceptance criteria, and generates a comprehensive review report with actionable issues.

Can I update task status to done automatically when a code review is approved?

Yes, when a code review is approved, the workflow marks tasks as done and updates tasks.md to reflect completed reviews and decisions. This keeps task statuses in sync with review outcomes for auditable tracking.

What is the best way to review all pending code changes on a feature branch?

The best way to review pending changes is to run a structured review workflow on your feature branch. Specify task IDs to review or evaluate all pending work, mapping changes to specifications and verifying documentation where available.

Does a structured code review workflow verify documentation and tests?

Yes, a structured code review workflow verifies documentation and tests where available. It applies a structured evaluation across code changes, ensures alignment with acceptance criteria, and reports findings with actionable issues for completed implementations.

Do I need task IDs to start a structured code review?

No, task IDs are not required to start a structured code review. You can identify the review target by task ID or review all pending work, making the workflow flexible for both targeted and comprehensive branch evaluations.