Analyze software issues and generate implementation prompts with RCA markdown files.
npx skills add https://github.com/fluxforgeai/ARTEMIS --skill rca-bugfix
Please help me install this Agent Skill. Skill: rca-bugfix Source: https://github.com/fluxforgeai/ARTEMIS/tree/main/.claude/skills/rca-bugfix Command: npx skills add https://github.com/fluxforgeai/ARTEMIS --skill rca-bugfix
This Skill guides engineers through structured root cause analysis for software bugs, consolidating evidence, documenting findings, and producing a clear implementation prompt so teams can move quickly from discovery to remediation.
Run /rca-bugfix with a concise issue description such as "health check timeout causing gray indicators on monitor page" to draft an RCA and an implementation prompt.
High-intent search queries and answers about installing and using this skill.
To generate a developer-ready implementation prompt after root cause analysis, run the Skill with an issue description so it loads investigation artifacts, writes RCA markdown files to docs/RCAs, and outputs fix prompts to docs/prompts.
Documenting software bug evidence and triage findings in a repository is done by consolidating logs and code evidence into standardized RCA markdown files written directly to the docs/RCAs directory.
Yes, you need existing investigation artifacts or a completed initial finding step for bug triage, because the workflow validates these prerequisites before reviewing evidence and designing the fix.
Structured root cause analysis transitions from bug discovery to remediation by confirming the underlying cause, capturing code evidence, and producing an implementation prompt for the downstream planning step.
Yes, you can enforce filename conventions for RCA documents and fix prompts in your pipeline, as the workflow enforces naming and pipeline rules for markdown files saved to docs/RCAs and docs/prompts.
Root cause analysis workflows require validating prerequisites to ensure investigation artifacts exist, preventing incomplete evidence reviews and ensuring accurate RCA documents and implementation prompts are generated.
jlawsTriage GitHub issues and generate pull requests with root-cause analysis.
YomiamyGenerate structured markdown spec files from issue documents and code observations.
EvilBit-LabsGenerate CodeTour .tour JSON artifacts anchored to file and line ranges.
HouseofmvpsTrace software bugs to root causes using evidence-based investigation protocols.
