skills.rest
C-ra-ZY
C-ra-ZYCOMMUNITY
Explore all skills by this author →
GitHub

carl-dev-flow-review-loop

Coordinate iterative code-review cycles with memo-based reviews and fix re-review loops.

1|Updated Mar 11, 2026
Search Tags:#automation#workflow#collaboration#iteration#code-review#memo
One-click install
npx skills add https://github.com/C-ra-ZY/carl-dev-flow-skills --skill carl-dev-flow-review-loop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: carl-dev-flow-review-loop
Source: https://github.com/C-ra-ZY/carl-dev-flow-skills/tree/main/skills/carl-dev-flow-review-loop
Command: npx skills add https://github.com/C-ra-ZY/carl-dev-flow-skills --skill carl-dev-flow-review-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating iterative code-review cycles to ensure code quality and delivery readiness across stakeholders by formalizing memo creation, review rounds, and iterative fixes.

Core Features & Use Cases

  • Structured review memo generation and tracking across iterations
  • Delegation of fixes to sub-agents and re-review orchestration
  • In-workflow artifact storage in .carl/review for traceability
  • Guidelines for regression verification in bug-fix scenarios

Quick Start

Load carl-dev-flow-review-loop and start the recursive review loop with your code artifact.

Frequently Asked Questions about carl-dev-flow-review-loop

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

FAQPage Schema
How do I coordinate iterative code-review cycles across multiple stakeholders?▼

Iterative code-review cycles are coordinated using memo-based reviews, fix decomposition, and re-review loops across stakeholders within OpenCode workflows to drive deliverable software quality.

How does memo-based code review work in an automated workflow?▼

Memo-based code review works by generating structured review memos, delegating fixes to sub-agents, and orchestrating re-review loops while storing artifacts in .carl/review for traceability.

Can I track code review artifacts and iterations within OpenCode workflows?▼

Yes, you can track code review artifacts and iterations within OpenCode workflows by storing structured review memos and iterative fix records in the .carl/review directory.

How do I decompose code review fixes for sub-agents in an iterative loop?▼

Code review fixes are decomposed for sub-agents by breaking down review memo feedback into actionable tasks, delegating them, and orchestrating re-review loops until quality is met.

What is the best way to manage regression verification in iterative bug-fix scenarios?▼

Managing regression verification in iterative bug-fix scenarios requires applying structured review memos and following specific guidelines for regression verification during re-review loops.

Related Skills

Explore More Software Engineering Skills→
gabrielkoerichgabrielkoerich
5

skill-creator

Generate a new skill directory with SKILL.md frontmatter and optional folders for scripts, references, assets.

Community
Basic
StudentCristianStudentCristian

nw-par-review-criteria

Enforce quality dimensions and review artifacts across DevOps phases.

Community
Advanced
DicklesworthstoneDicklesworthstone
70

agent-swarm-workflow

Coordinate parallel software tasks across multiple agents using Agent Mail and BV prompts.

Community
Advanced
clevergadgetclevergadget

code-reviewer

Review local changes and remote Pull Requests using Git and GitHub CLI.

Community
Intermediate