skills.rest
chrono-meta
chrono-metaCOMMUNITY
Explore all skills by this author →
GitHub

convergence-loop

Iterates FAIL-FIX-reverify cycles until configurable pass criteria are met.

7|Updated May 26, 2026
Search Tags:#quality assurance#code review#workflow orchestration#gate validation#convergence-loop#iterative verification#fail-fix cycle
One-click install
npx skills add https://github.com/chrono-meta/forge-harness --skill convergence-loop-chrono-meta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: convergence-loop
Source: https://github.com/chrono-meta/forge-harness/tree/main/plugins/fh-commons/skills/convergence-loop
Command: npx skills add https://github.com/chrono-meta/forge-harness --skill convergence-loop-chrono-meta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Single-pass gate checks are unreliable because fixes often introduce new, hidden failures, leading to false "passed" results that cause downstream rework and missed defects.

Core Features & Use Cases

  • Iterative Convergence Cycles: Runs repeated FAIL→FIX→re-verify rounds up to a configurable maximum, only declaring a gate truly passed after 2 consecutive clean rounds to eliminate false positives.
  • Structured Escalation: Automatically classifies non-convergence root causes (ambiguous criteria, FIX capability limits, gate design flaws) and recommends targeted corrective actions.
  • Universal Applicability: Works with any verification checkpoint including code quality gates, audit steps, session harvest loops, and custom FAIL→FIX workflows.

Quick Start

Use the convergence-loop skill to run iterative verification rounds on your [gate name] checkpoint until all items pass or escalation is required.

Frequently Asked Questions about convergence-loop

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

FAQPage Schema
Why do single-pass code quality gates return false positive results?▼

Single-pass gate checks fail because applied fixes often introduce new hidden failures, causing false passed results and downstream rework that iterative verification prevents.

How do I implement iterative fail-fix cycles for workflow orchestration?▼

Implement iterative fail-fix cycles by running repeated FAIL→FIX→re-verify rounds up to a configurable maximum limit, only declaring a gate truly passed after consecutive clean rounds.

Does convergence-loop work with custom audit workflows and session harvest loops?▼

Yes, convergence-loop works universally with any verification checkpoint including code quality gates, audit steps, session harvest loops, and custom fail-fix repeating structures.

What is the best way to handle non-convergence in gate validation?▼

Handle non-convergence in gate validation by using structured escalation pathways that classify root causes like ambiguous criteria or fix capability limits and recommend targeted corrective actions.

When should I not use single-pass verification for code review?▼

Avoid single-pass verification for code review when fixes might create new hidden failures, requiring iterative convergence cycles with configurable maximum round limits and immutable pass criteria instead.

Related Skills

Explore More Software Engineering Skills→
yannicklothyannickloth

review-fix-typst-diagrams

Automates iterative Typst diagram review and fix cycles until zero critical/warning findings remain.

Community
Advanced
sayasaya8039sayasaya8039
2

quality-nonconformance

Guide non-conformance management, root cause analysis, and corrective action tracking for regulated manufacturing.

Community
Advanced
KiefBCKiefBC
1

code-reviewer

Detect and fix code quality issues across diverse codebases.

Community
Basic
shawnroosshawnroos

auto-preset

Dispatch a named preset against a target with ephemeral verification criteria.

Community
Intermediate