loop2converge

Runs, classifies, and fixes benchmark failures across IC design flows until targets pass.

26|8|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/vibeic/vibe-ic --skill loop2converge-vibeic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: loop2converge
Source: https://github.com/vibeic/vibe-ic/tree/main/vibe-ic-marketplace/plugins/vibe-ic/skills/loop2converge
Command: npx skills add https://github.com/vibeic/vibe-ic --skill loop2converge-vibeic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Benchmark runs in IC design flows produce FAILs that nobody systematically investigates, and fixes that never leave a local cache die with the session. This Skill closes the loop: it runs the canonical benchmark entry point, classifies every failure, fixes the layer that owns it, proves the fix, and captures it as a PR. ## Core Features & Use Cases - Failure classification: Sorts every FAIL into flow, gate, or tool categories, each with a distinct owner and repository, preventing fixes in the wrong layer. - Cache-based proof: Patches the installed plugin cache and validates fixes against real artefacts with bidirectional falsification and a control input before any repo PR. - Closed convergence loop: Re-runs after upgrade and session restart until the subject's target is met, whether that is flow_compliance_check exit 0, LEF/GDS deliverables, or the highest honest pass@1. - Use Case: After a /vibe-ic-all run on a benchmark IC reports failures, use this Skill to classify each FAIL, fix the owning layer in the vibe-ic plugin or vibeic-eda fork, prove the fix in the cache, and re-run until convergence. ## Quick Start Run the loop2converge skill to converge the latest benchmark run by classifying every FAIL and fixing the layer that owns it.

Frequently Asked Questions about loop2converge

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

FAQPage Schema
How do I fix a failing IC design benchmark run?▼

Run the canonical front door (/vibe-ic-all or /vibe-ic-benchmark), then classify every FAIL as flow, gate, or tool before changing anything. Fix the layer that owns the defect, prove it in the plugin cache against real artefacts, and capture it as a PR to the owning repo.

What is the difference between flow, gate, and tool failures?▼

Flow failures are wrong step ordering or gating in the flow yaml and runner. Gate failures are checker verdicts that do not follow from evidence, owned by programs/*_check.py. Tool failures are defects in the EDA binary itself, fixed in the vibeic-eda fork.

Why does the benchmark still fail after upgrading the plugin?▼

An MCP server keeps serving the plugin version it booted with, so an upgrade does not reach a running server. Read back plugin_programs_dir via eda_doctor and restart the session so the MCP re-registers before re-running.

Can I edit the installed plugin cache to carry a fix into a run?▼

No. The cache is where a fix is proven against real artefacts, never where it lives. A cache edit that reaches a run makes the benchmark number describe a tree that exists on only one machine.

When should a benchmark FAIL be declared N/A or waived?▼

Declare N/A only when a check genuinely does not apply to the route or PDK, quoting the yaml clause. Waive only when a capability is missing, and always attach evidence, a ticket id, and review_required: true.

What counts as a converged benchmark run?▼

Convergence means the subject's own target is met: flow_compliance_check exit 0 for benchmark ICs, LEF/GDS deliverables for IP cells, or the highest honest pass@1 for open benchmarks. An honest FAIL naming a real unrepaired violation also counts as converged.