Document failure evidence and isolate root causes with hypothesis testing.
npx skills add https://github.com/karitham/dotfiles --skill debugging-karitham
Please help me install this Agent Skill. Skill: debugging Source: https://github.com/karitham/dotfiles/tree/main/modules/opencode/skills/debugging Command: npx skills add https://github.com/karitham/dotfiles --skill debugging-karitham
Systematic debugging protocol emphasizing empirical investigation over code reasoning to avoid incorrect conclusions and reduce wasted time. It guides observers to collect concrete evidence from logs, tests, and history, forms precise hypotheses, and designs experiments to distinguish between competing explanations.
Observe system behavior, formulate hypotheses, and design targeted experiments to isolate the root cause.
High-intent search queries and answers about installing and using this skill.
Empirical debugging isolates root causes by collecting concrete evidence from logs and traces, forming precise hypotheses, and running targeted experiments to distinguish between competing explanations for system crashes.
Debugging flaky tests requires empirical observation of runtime outputs and version history to identify exact failure behaviors, followed by iterative hypothesis testing to isolate environmental or configuration variables causing the inconsistency.
Create minimal reproductions by observing system behavior to document exact failures, formulating hypotheses based on empirical evidence, and designing controlled experiments that reliably trigger the unexpected behavior for diagnosis.
Incorrect conclusions often result from relying on code reasoning over empirical investigation; systematically gathering concrete evidence from logs, tests, and history, then testing hypotheses, prevents wasted time and false diagnoses.
Yes, hypothesis-driven experiments narrow the failure space by applying minimal, verifiable tests across code, configuration, and environment to isolate whether configuration mismatches are the actual root cause of the observed failure.
Empirical debugging is less effective when runtime logs, traces, or test outputs are unavailable, as the methodology depends on gathering concrete evidence and observing exact failure behaviors to formulate and test hypotheses.
derHakenTrace data flow and apply a four-phase process to fix root causes.
arvindbattulaDiagnose root-cause failures with a structured triage workflow.
readycheck-devExtract user observations from ADA transcripts and correlate them with trace events and screenshots.
OneWave-AIReview code for security vulnerabilities, performance bottlenecks, and maintainability issues.
