review-step

Invoke a reviewer agent to validate a build step and produce approval or feedback.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lenlla/one_shot_build --skill review-step-lenlla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-step
Source: https://github.com/lenlla/one_shot_build/tree/main/skills/review-step
Command: npx skills add https://github.com/lenlla/one_shot_build --skill review-step-lenlla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually invoke a reviewer agent to validate the work produced for a specific epic and step when the normal build-step review flow is not appropriate or when an automated review must be re-run.

Core Features & Use Cases

  • Determine context: Locate the active epic and step from execution state or accept explicit arguments to target a specific execution.
  • Change detection: Compute the git diff since the last approved step or TDD baseline to scope the review.
  • Reviewer orchestration: Dispatch the reviewer subagent with the Task tool, providing the step specification, diff, test results, and review criteria, then process the review output to mark approval or surface requested changes.
  • Use Case: When a developer iterates on a model step outside the automated pipeline, run this Skill to get a formal reviewer verdict and update execution state accordingly.

Quick Start

Run the review-step skill to invoke the reviewer agent for the current epic and step, collect the git diff and test results, and produce an approval or requested-changes response.

Frequently Asked Questions about review-step

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

FAQPage Schema
How do I manually run a code review for a specific git build step?

To manually run a code review, invoke the reviewer agent to validate the current build step's work, compute the git diff, and produce an approval or requested changes response.

Can I re-run an automated code review outside the normal build pipeline?

Yes, you can re-run an automated code review outside the normal pipeline by dispatching the reviewer agent for a specific epic and step to validate work and update the execution state.

What do I need to dispatch a reviewer subagent for code review?

To dispatch a reviewer subagent you need repository git history access, the execution state file, test results, and a Task tool capable of updating execution state with approval or feedback.

How does the reviewer agent determine what code changes to validate?

The reviewer agent validates code changes by computing the git diff since the last approved step or TDD baseline to scope the review and provide the step specification for formal validation.

When should I manually trigger a code review instead of using the automated flow?

Manually trigger a code review when the normal build-step review flow is not appropriate, or when you need to re-run automated reviews for a specific epic and step after iterating outside the pipeline.

What happens to the execution state after a manual code review completes?

After a manual code review completes, the reviewer output is processed to mark approval or surface requested changes, and the execution state file is updated accordingly to reflect the verdict.