investigate-first

Diagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, performance regressions, or investigations needing evidence-ranked hypotheses.

109,632
installs: 0 up / 0 down, score 0.00
votes: 115,798
repo stars
Updated: less than a month ago
In the catalog since: 18 Sept 2026
From: juliusbrussee/caveman

Get it through your agent npx skills add juliusbrussee/caveman@investigate-first

Skill instructions

Rendered from the published SKILL.md, 12 lines.

Investigate first

Gather evidence before changing product code.

Separate observed symptom from inferred cause.
Trace inputs, state transitions, ownership boundaries, and failure output.
Rank hypotheses by evidence and cheap falsification value.
Do not edit until one credible mechanism explains evidence.
Stop exploration when evidence is sufficient to name cause or exact blocker.

Report cause and proof. Make no fix unless task authorizes implementation.

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "investigate-first"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository juliusbrussee/caveman
Listing on skills.sh

From juliusbrussee/caveman via skills.sh

Related skills

systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
313,293 installs
diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
227,595 installs
diagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
863,551 installs
surgical-patch
Fix bugs and small behavior changes at the narrowest responsible layer. Use when regression proof, preserved surrounding behavior, and task-relevant tests matter.
108,978 installs
safe-debug
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
340,962 installs