investigate-bug-report SKILL.md skillA
investigate-bug-report from atman-33/workhub is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add atman-33/workhub/investigate-bug-report@git:20260711.1990e28Pins git:20260711.1990e28 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- atman-33/workhub
- Path
plugins/engineering/skills/investigate-bug-report/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260711.1990e28, committed Jul 11, 2026
- Size
- 3,209 bytes
- Repository stars
- 3
- License
- MIT
Investigate a reported bug to its root cause — reproduce, trace the code path, identify the defect with evidence, assess blast radius, and propose fix candidates without changing code. Use when the user reports or pastes a bug/defect/unexpected behavior and wants it diagnosed, or asks "why is X happening".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Investigate Bug Report
Diagnose, don't fix. The deliverable is a root-cause finding with evidence —
apply a fix only if the user then asks.
## Steps
1. **Pin down the report.** Extract from the report (ask only for what's
missing and blocking): observed behavior, expected behavior, steps or
input that trigger it, environment/version if relevant.
- Completion criterion: you can state "given X, it does Y, but should do Z"
in one sentence.
2. **Reproduce — or trace when you can't.** Prefer an actual reproduction
(run the failing command, a minimal script, or an existing test tightened
to the case). When reproduction isn't feasible (needs external services,
prod-only data), trace the code path statically from the entry point the
report implies, and say the diagnosis is trace-based.
- Completion criterion: the failure is observed firsthand, or the full
path from trigger to symptom is traced with `file:line` hops.
3. **Isolate the root cause.** Follow the data from symptom back to the first
point where state or logic diverges from intent. Distinguish the **root
cause** from where the error surfaces — they are usually different lines.
…Read the whole file at its exact version.
How to install
mdr add atman-33/workhub/investigate-bug-report@sha256:b78864b9cc1d7988The line at the top of this page pins the label git:20260711.1990e28, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ffauwqvnxvatkqoy)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 11, 2026.
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 (3209 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
atman-33/workhub · 3 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ffauwqvnxvatkqoy GET https://markdownregistry.com/api/v1/resolve?ref=atman-33/workhub/investigate-bug-report GET https://markdownregistry.com/api/v1/blob/b78864b9cc1d79884a5197533865b6a86bde634ca0f81b457ee3ce1818f0875e
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.