wrought-rca-fix

Automate an RCA bugfix loop with verifier-driven test verification.

3|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/fluxforgeai/ARTEMIS --skill wrought-rca-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrought-rca-fix
Source: https://github.com/fluxforgeai/ARTEMIS/tree/main/.claude/skills/wrought-rca-fix
Command: npx skills add https://github.com/fluxforgeai/ARTEMIS --skill wrought-rca-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start an autonomous RCA bugfix loop with test verification that ensures fixes are validated through a predefined verifier and progress is tracked automatically.

Core Features & Use Cases

  • Stepwise RCA identification: Detects active RCA loops, reads RCA reports, and initiates a structured bugfix cycle with verifier checks.
  • Stateful execution: Maintains loop state in .claude/wrought-loop-state.json, including tracking iterations, time stamps, and history.
  • Verifier-driven completion: Applies fixes and automatically runs configured verifications until the RCA is resolved.

Quick Start

Initiate the RCA fix loop by selecting an RCA report and starting the verifier-driven iteration.

Frequently Asked Questions about wrought-rca-fix

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

FAQPage Schema
How do I automate root-cause analysis and bugfix verification in a loop?

Autonomous root-cause analysis and bugfix verification is automated by reading RCA reports, applying iterative fixes, and running configured test verifiers until the issue is resolved and completion is reported.

How does an automated RCA bugfix loop track iteration state and history?

An automated RCA bugfix loop tracks iteration state and history by maintaining execution records, time stamps, and iteration counts in a dedicated loop state JSON file throughout the debugging cycle.

Can I use a custom test verifier to validate iterative bugfixes automatically?

You can use a custom test verifier to validate iterative bugfixes by configuring the verifier initialization, which automatically runs tests after applying each fix until the RCA is resolved.

What is the best way to manage an iterative debugging workflow with automatic verification?

The best way to manage an iterative debugging workflow with automatic verification is using a stateful loop that applies fixes and executes verifier checks continuously until the root-cause is eliminated.

What happens if my automated RCA fix loop does not resolve the bug?

If an automated RCA fix loop does not resolve the bug, the stateful execution continues tracking iterations and applying fixes while running configured verifications until completion criteria are met.