Trace software bugs to root causes using git history and structured reasoning.
npx skills add https://github.com/fysoul17/ian-on-v1 --skill devlyn-resolve
Please help me install this Agent Skill. Skill: devlyn:resolve Source: https://github.com/fysoul17/ian-on-v1/tree/main/ian-on/.claude/skills/devlyn%3Aresolve Command: npx skills add https://github.com/fysoul17/ian-on-v1 --skill devlyn-resolve
This Skill helps you systematically identify the true root cause of a reported bug or failure so fixes address the underlying problem instead of symptoms.
Provide the exact issue details (error message or failing behavior) as the value of $ARGUMENTS, then ask for root cause analysis and a fix plan.
High-intent search queries and answers about installing and using this skill.
To debug to the root cause, you trace from observed symptoms to fundamental causes using evidence-based analysis. This involves git blame investigation, execution-path tracing, and structured 5 Whys reasoning to identify the true origin of failures.
Finding a regression commit requires git log and blame investigation to pinpoint when and how the issue was introduced. By tracing the execution path and inspecting targeted code history, you can identify the specific change responsible for the failure.
Fixing a multi-module bug requires evidence-based root cause analysis to select among competing hypotheses. When hypotheses cannot be ruled out through systems reasoning, the best approach is escalating to a team resolver for broader investigation.
Yes, plan-first remediation performs the root cause analysis first, then enters plan mode. This allows you to review and approve the proposed production-grade fix with tests before any code modifications are actually implemented.
Root cause analysis applies to incident response by combining regression identification with structured 5 Whys reasoning. It culminates in a production-grade fix with tests, ensuring the test-driven fix addresses the fundamental cause rather than temporary symptoms.
ryu-satoDiagnose software implementation failures by consolidating evidence and runtime state.
lionbenjaminDiagnose and fix codebase bugs with root-cause analysis and regression tests.
DriveConnect-alphaDiagnose software issues through a 4-phase debugging workflow with root-cause analysis.
Himanshu040604Investigate multiple root cause hypotheses in parallel using ACH methodology.
