ralpha-loop

Implement code changes and iterate with a persistent reviewer until zero findings remain.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/Idate96/codex_skills --skill ralpha-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralpha-loop
Source: https://github.com/Idate96/codex_skills/tree/main/skills/ralpha-loop
Command: npx skills add https://github.com/Idate96/codex_skills --skill ralpha-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes agents (resource) components.

What problem does it solve?

This Skill automates a rigorous implement-test-review cycle for coding tasks, ensuring code quality and adherence to requirements through strict, iterative feedback.

Core Features & Use Cases

  • Automated Iteration: Manages a loop of implementation, testing, and review until all findings are resolved.
  • Persistent Reviewer: Reuses the same reviewer agent across all iterations to maintain context and consistency.
  • Structured Findings: Tracks and addresses reviewer feedback systematically.
  • Use Case: When asked to implement a new feature, this Skill will write the code, run tests, send it to a reviewer, address any feedback, and repeat until the reviewer is satisfied.

Quick Start

Use the ralpha-loop skill to implement the requested code changes and iterate with the reviewer until no findings remain.

Frequently Asked Questions about ralpha-loop

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

FAQPage Schema
How do I automate the code review and testing loop for new feature implementation?

To automate the code review and testing loop, this Skill implements a deterministic process that writes code, runs tests, and requests review, repeating until the reviewer has zero findings.

What is a persistent reviewer agent and how does it improve iterative coding?

A persistent reviewer agent is reused across all iteration cycles to maintain context and consistency. It improves iterative coding by systematically tracking findings in a structured ledger until all issues are resolved.

How do I ensure code quality through strict iteration until a reviewer finds no issues?

You ensure code quality by using an automated implement-test-review cycle that requires a persistent reviewer agent and a structured findings ledger to manage strict iteration until the reviewer is satisfied.

Do I need a structured findings ledger to manage iterative code review cycles?

Yes, a structured findings ledger is required for effective cycle management. It systematically tracks and addresses reviewer feedback during the implement-test-review loop to ensure all findings are resolved.

Why does my automated coding loop keep failing the review phase?

Your automated coding loop may fail the review phase if the reviewer agent identifies unresolved findings. The loop is designed to repeat implementation, testing, and review until the reviewer reports zero findings.

What's the best way to manage reviewer feedback during automated code implementation?

The best way to manage reviewer feedback is through a structured findings ledger that tracks issues systematically, allowing the implement-test-review loop to address all findings before completing the coding task.