review-cycle

Execute three-mode code review cycles with session, module, or fix scopes.

1|Updated May 12, 2026

Search Tags:#quality assurance #code review #workflow automation #routing #module review #fix validation #chained execution

Ready to run

npx skills add https://github.com/tcytan/tecton --skill review-cycle-tcytan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-cycle
Source: https://github.com/tcytan/tecton/tree/main/.claude/workflow-skills/review-cycle
Command: npx skills add https://github.com/tcytan/tecton --skill review-cycle-tcytan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review cycles often waste time by using the same broad review approach for every change, slowing down sessions and delaying fixes.

Core Features & Use Cases

3-mode routing: Selects the right review path for session-wide review, focused module review, or targeted fix review.
Deterministic chain execution: Runs the appropriate phased workflow via a chain loader entry and keeps the process consistent.
Review outcome tracking: Uses review_status and fix_count to summarize progress and results across phases.

Use it when you need to quickly switch between broad code quality review, module-scoped architectural review, or verifying specific fixes without running the entire review from scratch.

Quick Start

Run the chain-loaded review cycle for session-level review by executing: chain_loader start --chain=ccw-review-cycle --entry=session.

Frequently Asked Questions about review-cycle

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

FAQPage Schema

How do I automate code review workflows based on change scope?▼

Automated code review workflows route execution through three modes—session, module, or targeted fix—based on the change scope. This ensures the review granularity matches the context, preventing broad reviews from slowing down focused fixes.

What is the best way to run a focused module review without re-checking the entire session?▼

Focused module review runs by selecting the module mode, which executes a scoped architectural review. This bypasses the broader session-wide checks to isolate evaluation to the specific module boundaries.

How does review status tracking work across the gather, fix, and verify phases?▼

Review status tracking maintains review_status and fix_count variables across gather, review, fix-apply, verify, and reporting phases. This deterministic chain execution summarizes progress and reports the final outcome.

Can I use chain-loaded routing to switch between session-wide and targeted fix reviews?▼

Chain-loaded routing supports switching review paths by executing the ccw-review-cycle chain loader with specific mode entries. You select session, module, or fix entry points to direct the deterministic workflow.

When should I avoid using a single broad code review approach for all changes?▼

Avoid broad code review approaches for targeted fixes or isolated module changes, as applying session-wide review uniformly wastes time and delays fixes by evaluating irrelevant, unchanged code.