Reproduce bugs and document root causes with file:line evidence.
npx skills add https://github.com/chughtapan/safer-by-default --skill investigate-chughtapan
Please help me install this Agent Skill. Skill: investigate Source: https://github.com/chughtapan/safer-by-default/tree/main/skills/investigate Command: npx skills add https://github.com/chughtapan/safer-by-default --skill investigate-chughtapan
Reproduce and document bugs by reproducing failures, isolating the failing code path, and naming the root cause with file:line evidence. Produces a written writeup and a fix recommendation routed to the correct implementation modality. Use when a bug is reported, when production is misbehaving, or when a test fails for non-obvious reasons. Do NOT use to apply the fix; that is a separate modality. Investigation and remediation are different budgets.
Describe the bug and reproduce it deterministically, then publish the root-cause writeup with evidence.
High-intent search queries and answers about installing and using this skill.
Root-cause analysis for non-obvious test failures requires deterministic reproduction to reveal the failing code path, naming the root cause with concrete file:line evidence, and producing a formal writeup for remediation.
Documenting a production bug involves reproducing the failure deterministically, isolating the failing code path, and publishing a formal writeup that names the root cause with concrete file:line evidence.
Reproduce defects deterministically by collecting evidence and triggering the failure consistently to reveal the failing code path, which allows you to isolate the issue and name the root cause with concrete file:line evidence.
No, you should not use this investigation process to apply a code fix directly. Investigation and remediation are different budgets; this process diagnoses and documents the root cause, then routes the fix to a separate implementation modality.
Perform a structured investigation when bugs are reported, production misbehaves, or tests fail for non-obvious reasons. It isolates the failing code path and names the root cause with file:line evidence before routing remediation effort.
cslsoftwaresConvert informal bug reports into structured tickets with severity and reproduction steps.
EhsaanArkDiagnose software bug root causes through phase-based investigation and code tracing.
willdadyDiagnose software bugs through a structured six-phase feedback loop.
steadyfallDiagnose software defects through structured root-cause investigation workflows.
