What problem does it solve? Debugging often devolves into guesswork and repeated trial-and-error fixes that never address the real failure mechanism. This Skill enforces a disciplined four-part Root Cause Analysis (RCA) process so every bug fix is grounded in evidence, documented, and prevented from recurring. ## Core Features & Use Cases - Structured 4-Part RCA: Documents Symptom, Root Cause, Resolution, and Prevention & Learnings for every bug, producing an auditable record instead of an ad-hoc patch. - CI/CD Pipeline Diagnosis: Integrates with GitMap pipeline-ai commands to extract targeted failure lines (e.g., ##[error], compile errors) instead of dumping entire logs, and uses adaptive ETA-based waiting to avoid wasteful tight polling loops. - Persistent Issue Logging: Writes RCA reports to .ai-memory/issues/ for general bugs and .ai-memory/cicd-issues/ for pipeline failures, building an organizational knowledge base. - Use Case: A CI build fails with a cryptic error. The agent inspects the pipeline via gitmap pipeline-ai status --json, extracts only the failing lines, writes a 4-part RCA identifying the exact root cause, applies a minimal fix, and logs the prevention rule for future runs. ## Quick Start Ask the agent to diagnose the current failing test or CI pipeline failure and produce a root cause analysis before applying any fix.
