bug-hunting skillA
bug-hunting is agent-read markdown (skill) from rfxlamia/pocketto: Use when fixing bugs, debugging failures, or proactively reviewing code for hidden bugs. Reactive mode: fix known bugs. Proactive mode: hunt for bugs in code. Enforces confirmed root cause before any fix..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Bug Hunting ## Overview Bugs have root causes. Symptoms have patches. Patches create future bugs. **Core principle:** A claim is not evidence. Evidence is not root cause. Root cause is not a fix. **Violating the letter of this process is violating the spirit of bug hunting.** ## Two Modes | Mode | Trigger | First Question | |------|---------|----------------| | **Reactive** | "Fix this bug", "test failing", "production error" | What is the confirmed root cause? | | **Proactive** | "Review this code", "find bugs in...", "audit this" | What could go wrong? Where are the weakest points? | Both modes follow the same 5 phases. Entry point differs; discipline does not. ## The Three Iron Laws ``` LAW 1: NO FIX WITHOUT CONFIRMED ROOT CAUSE LAW 2: NO CLAIM WITHOUT EVIDENCE LAW 3: FIX THE SOURCE, NOT THE SYMPTOM ``` **The Laws are non-negotiable. All three must hold for every bug.** If you haven't confirmed root cause → you cannot propose a fix. If you have evidence → state it explicitly. Never say "probably" or "almost certainly." If the fix is at the crash site → trace back further. The source is upstream. ## The Five Phases …
Read the whole file at its exact version.
How to install
mdr add rfxlamia/pocketto/bug-hunting@git:20260525.58ede9cmdr add rfxlamia/pocketto/bug-hunting@sha256:0fa9cf39bcea9079Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_cgdammyf4cvznxh4)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7154 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
rfxlamia/pocketto · 5 stars · license MIT · pushed 2026-09-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cgdammyf4cvznxh4 GET https://markdownregistry.com/api/v1/resolve?ref=rfxlamia/pocketto/bug-hunting GET https://markdownregistry.com/api/v1/blob/0fa9cf39bcea90792484bde4ffa7126645ec3e9c5d7a12dc65a97c146616117e
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from rfxlamia/pocketto
Every file in rfxlamia/pocketto