loop-repair

Classify failing verification outputs and apply bounded repairs to agent runs.

1|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/SollanSystems/loop-engineer --skill loop-repair
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop-repair
Source: https://github.com/SollanSystems/loop-engineer/tree/main/skills/loop-repair
Command: npx skills add https://github.com/SollanSystems/loop-engineer --skill loop-repair

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps recover agent runs that have failed verification, avoiding endless thrashing by forcing a disciplined, evidence-based repair process.

Core Features & Use Cases

  • Failure Classification: Distinguishes deterministic failures, rubric failures, flaky checks, regressions, spec gaps, and environmental blockers.
  • Bounded Repair Workflow: Makes the smallest possible fix, reruns the same check, and records whether the change was productive.
  • Escalation and Safety: Caps retry attempts, avoids scope creep, refuses test manipulation, and escalates to replan, revert, approval, or termination when needed.
  • Use Case: A test suite turns red after an agent patch; this Skill identifies the likely failure mode, applies one targeted repair, and confirms whether the fix actually improved verification.

Quick Start

Use the loop-repair skill to inspect the failing verification output, classify the failure mode, apply the smallest bounded fix, and rerun the same check.

Frequently Asked Questions about loop-repair

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

FAQPage Schema
How do I fix failing tests after an agent run without causing endless thrashing?

To fix failing tests without thrashing, apply a bounded repair process that classifies the failure, makes the smallest possible diff, and reruns the same check. This enforces a disciplined, evidence-based recovery for failed agent runs.

What is the best way to handle broken verification outcomes in looped software workflows?

Handling broken verification outcomes requires classifying failures into deterministic errors, flaky checks, or spec gaps, then applying targeted minimal diffs. This structured approach confirms whether the repair actually improved verification.

How do I stop an agent from weakening tests or manipulating the spec when repairs fail?

To stop an agent from weakening tests, use a safety framework that refuses test manipulation and caps retry attempts. It escalates unresolvable failures to replan, revert, approval, or termination instead of allowing scope creep.

Can I use a bounded repair workflow for flaky checks and regressions?

Yes, a bounded repair workflow supports flaky checks and regressions by distinguishing them from deterministic failures. It applies one targeted repair and records whether the change was productive before attempting independent re-verification.

When should I escalate a failing loop repair instead of applying another patch?

You should escalate a failing loop repair when retry attempts hit the cap or the failure mode indicates an environmental blocker. The process escalates to replan, revert, approval, or termination to avoid unproductive scope creep.