app-bug-forensics skillA
app-bug-forensics is agent-read markdown (skill) from sidiangongyuan/codex-skills-library: Use when diagnosing or fixing user-reported application bugs. Guides evidence-backed root-cause analysis from symptoms, screenshots, logs, provider failures, background tasks, storage, or desktop lifecycle behavior through a scoped patch and regression tests..
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
# App Bug Forensics
Use this skill when a user reports a bug, screenshot, intermittent failure, or
confusing app behavior. The goal is root cause first, patch second.
## Workflow
1. Preserve the symptom.
- Identify the exact screen, action sequence, visible message, and affected
data scope.
- Inspect screenshots and logs when available.
- Do not assume the visible error string names the real failing component.
2. Trace the path.
- Follow the request from UI event to state store, API client, backend route,
persistence, sidecar/process boundary, and external provider when relevant.
- Search for all places that can set the visible error state.
- Check whether the failing request still belongs to the current selection.
- For AI failures, identify the exact provider, model, transport, profile,
credential source, timeout, and whether the request reached the provider.
3. Classify likely root cause.
- Stale async request or route watcher race.
- Frontend/backend version mismatch or old sidecar process.
- Missing optional capability being treated as fatal.
- Provider protocol, model, key, base URL, or auth mismatch.
…Read the whole file at its exact version.
How to install
mdr add sidiangongyuan/codex-skills-library/app-bug-forensics@git:20260712.ef71354mdr add sidiangongyuan/codex-skills-library/app-bug-forensics@sha256:a7dcf71b5b0ed9c9Pin 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_fszepcddisrl2v2t)
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 (4339 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
sidiangongyuan/codex-skills-library · 9 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fszepcddisrl2v2t GET https://markdownregistry.com/api/v1/resolve?ref=sidiangongyuan/codex-skills-library/app-bug-forensics GET https://markdownregistry.com/api/v1/blob/a7dcf71b5b0ed9c930cf47a44d6a4aea100d2ab57189d639587a626cc06559e9
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.