agentleFS
imMamdouhaboammarimMamdouhaboammar/deep-digger/.cursor/rules/deep-digger.mdc

deep-digger / rules

Cursor rule2 starsChanged 17 days agoMITView on GitHub

Deep Digger root-cause investigation, controlled falsification, and delta debugging

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 4,243 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

The file

We split this deep-digger.mdc into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When investigating stubborn, flaky, intermittent, or high-impact failures:

    line 9
  2. Distinctive:

    Never confuse symptom with root cause.

    line 10
  3. Distinctive:

    Use discriminating experiments before patching.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
deep-digger.mdc
---
description: Deep Digger root-cause investigation, controlled falsification, and delta debugging
globs: *
alwaysApply: false
---

# Deep Digger | Catch That Bug

When investigating stubborn, flaky, intermittent, or high-impact failures:
- Never confuse symptom with root cause.
- Maintain competing causal hypotheses.
- Use discriminating experiments before patching.
- Validate causal fixes via baseline reproduction, intervention, reversal, and negative control (A/B/A/C).

## CLI Quickstart
```bash
# Initialize case ledger
deep-digger init cases/incident-01

# Add competing hypotheses
deep-digger hypothesis cases/incident-01 add H1 "Race condition in cache eviction"
deep-digger hypothesis cases/incident-01 add H2 "Stale DNS TTL resolution"

# Generate evaluation report
deep-digger report cases/incident-01 --format text
```

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.