Investigate-first debugging discipline
Diagnose ambiguous failures with evidence-ranked hypotheses before touching a single line of code
- What
- Diagnose ambiguous failures with evidence-ranked hypotheses before touching a single line of code
- Cost
- Free
- Needs
- nothing — reference lookup only; no license declared in the source repo, so read it yourself before reusing its content
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a short pointer to @juliusbrussee's investigate-first method: a five-rule debugging discipline for ambiguous failures — separate the observed symptom from the inferred cause, trace inputs, state transitions, ownership boundaries and failure output, rank hypotheses by evidence and cheap falsification value, and make no fix until one credible mechanism explains the evidence, stopping exploration the moment the cause or the exact blocker is named. Honest caveats: **no license declared in the repository — license unknown**, so this is a short fiche linking to the source, without reusing its content; it is a process guide only, it ships no tooling or scripts. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: nothing — reference lookup only; no license declared in the source repo, so read it yourself before reusing its content Install "Investigate-first debugging discipline" for me. Fetch the SKILL.md from the source repository into a temporary folder, review it for anything suspicious, and report in two or three sentences what the investigate-first method covers (separating symptoms from inferred causes, tracing inputs and state transitions, evidence-ranked hypotheses, no fix until one credible mechanism explains the evidence) so I can apply the discipline to my own debugging. Do not copy the guide's content into my project — this is a reference lookup only. Repository: https://github.com/juliusbrussee/caveman/blob/main/skills/investigate-first/SKILL.md GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: don't touch anything outside the temp folder. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.