identify-bugs SKILL.md skillB
identify-bugs from tomzx/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tomzx/agents/identify-bugs@git:20261014.32cb919Pins git:20261014.32cb919 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tomzx/agents
- Path
skills/identify-bugs/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261014.32cb919, committed Oct 14, 2026
- First version recorded
- Oct 2, 2026
- Size
- 21,533 bytes
- Repository stars
- 12
- License
- MIT
Proactively discover latent bugs in an existing codebase (correctness, error handling, null and boundary handling, async, concurrency, state, resource management), keep only high-confidence ones, verify each where a seam exists, and use ghx to discard anything already tracked by a GitHub issue, searching for another candidate until nothing useful remains. Use when the user says /identify-bugs, "find bugs", "hunt for bugs", "look for latent bugs", "bug sweep", "what is broken", or wants a…
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
TODAY=!`date +%Y-%m-%d` REPO=!`git remote get-url origin 2>/dev/null | sed -E 's#.*[:/]([^/]+/[^/]+)(\.git)?$#\1#'` # Identify Bugs Reads an existing codebase and surfaces latent defects that are worth fixing and are not already tracked in the issue tracker. Every candidate must clear three gates: high confidence (the code path exists and is reachable), verification where possible (a failing test or runnable repro), and not already an existing GitHub issue. The dedup is what keeps the pass useful: the skill loads the issue history with `ghx` up front and re-checks each candidate, dropping anything tracked and continuing until no untracked bug remains. This is a proactive, whole-codebase hunt. It does not modify or commit source code. It produces a ranked bug report, and optionally files issues for the bugs that survive dedup. ## The Core Problem This Solves Bugs are usually found by accident, from a stack trace or a user report. A static scan in the other direction produces a pile of "probably a bug" claims, most of which are handled elsewhere, are by design, or are already known. Both directions waste effort. …
Read the whole file at its exact version.
How to install
mdr add tomzx/agents/identify-bugs@sha256:7fd12f789c4cf6edThe line at the top of this page pins the label git:20261014.32cb919, 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_slhqz2mjgvvvh5mx)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Oct 2, 2026 and Oct 14, 2026, about one every 4 days. Its first recorded version is graded A and its latest B.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.32cb919 latest | 2026-10-14 | 32cb919 | 21,533 B | B | view · diff |
| git:20261007.b35fc4b | 2026-10-07 | b35fc4b | 18,786 B | A | view · diff |
| git:20261004.00bb0c5 | 2026-10-04 | 00bb0c5 | 18,755 B | A | view · diff |
| git:20261002.df8fbe9 | 2026-10-02 | df8fbe9 | 18,762 B | A | view |
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (21533 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
tomzx/agents · 12 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_slhqz2mjgvvvh5mx GET https://markdownregistry.com/api/v1/resolve?ref=tomzx/agents/identify-bugs GET https://markdownregistry.com/api/v1/blob/7fd12f789c4cf6ed68feb942c46807cd1003c779ca13c7f1c6658ba326a127b2
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.