fix-loop

Diagnose failing commands, patch root causes, and verify with narrow rechecks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/StiensGate928/Srtforge --skill fix-loop-stiensgate928
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-loop
Source: https://github.com/StiensGate928/Srtforge/tree/main/.agents/skills/fix-loop
Command: npx skills add https://github.com/StiensGate928/Srtforge --skill fix-loop-stiensgate928

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fix-loop provides a structured approach to diagnosing and patching failing commands, ensuring root causes are identified, patches are verifiably effective, and failure domains are tracked for reproducibility.

Core Features & Use Cases

  • Diagnoses root causes of failing checks, builds, tests, or docs.
  • Patches root causes and reruns narrow checks to verify resolution.
  • Records failure domain and maintains traceability.

Quick Start

Rerun the failing command, patch the root cause, and verify the fix with a narrow recheck.

Frequently Asked Questions about fix-loop

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

FAQPage Schema
How do I diagnose the root cause of failing builds and tests?

To diagnose root causes of failing builds and tests, rerun the failing command to identify the specific failure domain, then apply a targeted patch and verify the resolution with a narrow recheck.

What is the best way to patch failing commands and verify the fix?

The best way to patch failing commands is to pinpoint the root cause first, apply a corrective patch, and then execute a narrow recheck of the specific failing check or test to confirm the resolution.

How do I verify a patch actually resolves a failing check without rerunning the entire suite?

You verify a patch by running a narrow recheck that targets only the specific failure domain originally recorded, ensuring the fix is effective without triggering the full validation suite.

Can I use this structured approach to fix both documentation validation and code build failures?

Yes, you can use this approach to fix both documentation validation and code build failures, as it applies to any failing command where you need to diagnose, patch, and verify the root cause.

Why does my patch keep failing verification after I apply a fix?

Your patch may keep failing verification because the true root cause was not diagnosed correctly, meaning the fix did not address the actual failure domain tracked during the initial diagnostic step.

Do I need any external dependencies to trace failure domains for reproducibility?

No external dependencies are required to trace failure domains, as the structured approach records the failure domain directly within your existing Codex workflows for full traceability and reproducibility.