review-cycle

Encode the review cycle as a state machine with per-stage templates.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/productengineered/parsely --skill review-cycle-productengineered
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-cycle
Source: https://github.com/productengineered/parsely/tree/main/.claude/skills/workflow/review-cycle
Command: npx skills add https://github.com/productengineered/parsely --skill review-cycle-productengineered

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical review cycle state machine, transition rules, and comment templates for all workflow stages. Use when advancing workflow state or writing review comments.

Core Features & Use Cases

  • State machine with defined transitions between stages (e.g., STARTING, TASK COMPLETED, READY FOR CODE REVIEW, CODE REVIEW PASSED, REJECTED, FIXED AND RESUBMITTED).
  • Per-stage templates for consistent reviewer comments and task updates.
  • Restart logic on any rejection to loop back to code-review to ensure a full cycle restart.

Quick Start

Follow the canonical lifecycle rules to progress a task through all stages using the provided templates and transitions.

Frequently Asked Questions about review-cycle

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

FAQPage Schema
How do I standardize a code review cycle with consistent state transitions?

Standardize a code review cycle by encoding the workflow as a state machine with defined stage transitions and per-stage comment templates. This enforces consistent handoffs and full traceability across all project management stages.

What is a state machine workflow for code review and when do I need it?

A state machine workflow for code review is a process automation model defining explicit transitions between stages like READY FOR CODE REVIEW and CODE REVIEW PASSED. You need it to eliminate ambiguous task handoffs and enforce a canonical lifecycle progression.

How do I enforce a full code review restart when a task is rejected?

Enforce a full code review restart by applying rejection logic that automatically loops any REJECTED task back to the code-review stage. This ensures the entire review cycle repeats from the beginning, maintaining end-to-end lifecycle coverage.

Can I use workflow templates for project management without manual state tracking?

Yes, you can use workflow templates for project management without manual state tracking by applying an automated state machine. The templates provide per-stage formatting for task updates and reviewer comments, while the state machine handles the progression logic automatically.

What's the best way to ensure traceable handoffs between code review stages?

The best way to ensure traceable handoffs between code review stages is to couple per-stage comment templates with a canonical state machine. This combination records standardized updates at each transition, creating a fully traceable lifecycle from TASK COMPLETED to CODE REVIEW PASSED.