Trace bugs from symptom to root cause with a phase-gated investigation workflow.
npx skills add https://github.com/Nairon-AI/flux --skill flux-rca
Please help me install this Agent Skill. Skill: flux-rca Source: https://github.com/Nairon-AI/flux/tree/main/skills/flux-rca Command: npx skills add https://github.com/Nairon-AI/flux --skill flux-rca
RCA provides a structured, end-to-end workflow to trace a bug from symptom to root cause, validate fixes with adversarial review, mandate regression testing, and embed learnings to prevent recurrence.
Initiate a root cause analysis for the reported issue and begin by reproducing the symptom.
High-intent search queries and answers about installing and using this skill.
Root cause analysis traces bugs from symptom to origin to support reliable fixes. Use it for production incidents requiring structured investigation, reproducibility, and post-fix verification to prevent recurrence.
Trace bugs by following a phase-driven workflow: reproduce, investigate, root cause, fix, verify, and learn. This structured approach enforces phase gates and risk assessment to validate fixes and embed learnings.
Validate fixes using adversarial review and production interrogation within a formal workflow. Mandate regression testing and post-fix verification to ensure robust changes and confirm the root cause is resolved.
Yes, root cause analysis supports production interrogation by enforcing a formal workflow with phase gates. It structures the investigation to reproduce symptoms and verify fixes directly against production behavior.
Fixes recur when investigations stop at symptoms instead of the root cause. A formal workflow with post-fix verification and an adversarial review phase embeds learnings to prevent incident recurrence.
gaebalaiCross-analyze logs, code, and Git history to identify root causes.
davekilleenGenerate structured incident post-mortems with root cause analysis and action items.
dhntDiagnose production errors by correlating logs, traces, and code paths.
ajsai47Investigate root causes before fixing bugs using a 4-phase workflow.
