fast-loop-coding

Run a plan-implement-dual-review-ship pipeline for small coding tasks.

3|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/qwwiwi/agentos-skills-public --skill fast-loop-coding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fast-loop-coding
Source: https://github.com/qwwiwi/agentos-skills-public/tree/main/skills/fast-loop-coding
Command: npx skills add https://github.com/qwwiwi/agentos-skills-public --skill fast-loop-coding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It removes the overhead of a full multi-phase coding workflow when you only need a small, well-scoped change, helping you reach a reviewed and shippable result faster.

Core Features & Use Cases

  • 4-phase micro-pipeline: a single-pass Plan, direct Implement with tests, dual-pass Review, and then Ship.
  • Dual Review for cheap insurance: parallel Codex (architecture/corner cases) and Opus code-reviewer (readability/patterns/test quality).
  • Clear scope guardrails: explicitly avoids unsafe/too-large work via an escape valve to the full loop-coding skill.

Quick Start

Tell Claude: "Apply fast-loop-coding to add a small CLI subcommand with inline tests and review, then commit and push the approved changes."

Frequently Asked Questions about fast-loop-coding

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

FAQPage Schema
How do I ship small code changes faster without running a full multi-phase workflow?

A fast coding loop accelerates small refactors and bug fixes by running a 4-phase micro-pipeline: plan, implement with tests, dual review, and ship. This removes the overhead of full multi-phase workflows, reaching a reviewed, shippable result in fewer steps.

How does dual code review work for isolated bug fixes?

Dual code review runs two parallel passes: one checks architecture and corner cases, while the other evaluates readability, coding patterns, and test quality. This parallel approach provides cheap insurance for small refactors by catching structural and style issues simultaneously.

Can I use this fast coding pipeline for large feature work across multiple subsystems?

No, this fast coding pipeline is built for single subsystems with a limited file and LOC scope. It includes strict phase constraints with a maximum of one fix iteration, making it unsuitable for large feature work or cross-system refactors.

What should I do if my small refactor grows beyond the defined scope limits?

If your small refactor exceeds the defined scope limits, trigger the escape mechanism to switch to the full loop-coding skill. This prevents unsafe or too-large work from proceeding through the constrained fast-track pipeline.

When should I choose a fast coding loop over a standard git workflow?

Choose a fast coding loop for short feature work, small refactors, isolated bug fixes with tests, and focused config rewrites. It accelerates these well-scoped tasks by enforcing strict phase constraints and skipping the research phase required in a standard git workflow.