correctness-hunt skillA
correctness-hunt is agent-read markdown (skill) from pisberg/vibetags: Run a bug hunt against this repository under a fixed work order - baseline the suite, hunt with named bug-shape lenses, failing-test-first, one commit per bug, suspicions reported separately, locks escalated never overridden. Use when the user says "correctness hunt", "bug hunt", "find bugs", "hunt for bugs", or asks for a systematic sweep for defects rather than a review of a specific diff..
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
# Correctness hunt
A hunt is not "look for bugs". It is a fixed, repeatable work order. Findings that skip a
step do not count.
## The work order
1. **Pull latest and branch.** Fresh branch per hunt (`fix/hunt-<date>` or similar), never
the default branch, based on up-to-date `origin/main`.
2. **Baseline before touching anything.** From `vibetags/`: `mvn test -Pe2e`, in the
background with output to a log (the run takes minutes and must not be truncated by a
tool timeout). Record the counts. A hunt against a red suite cannot separate findings
from pre-existing breakage; if the baseline is red, the hunt's first bug is the baseline.
3. **Hunt with named lenses**, not vibes. Each lens is a yes/no question asked of specific
code. The standing lens library, from the shapes that have actually bitten:
- **Drained evidence**: does any check read state that legitimately drains between the
moment of recording and the moment of judging? (The fingerprint/sidecar mtime coupling
is this repo's precedent.)
- **Re-registration wipes**: does re-running a registration/collection path clear state
…Read the whole file at its exact version.
How to install
mdr add pisberg/vibetags/correctness-hunt@git:20260815.32e6c75mdr add pisberg/vibetags/correctness-hunt@sha256:8718723a6f40ffb4Pin 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_xgvhnrbeb6vb2sso)
0 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 (3944 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
pisberg/vibetags · 25 stars · license MIT · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xgvhnrbeb6vb2sso GET https://markdownregistry.com/api/v1/resolve?ref=pisberg/vibetags/correctness-hunt GET https://markdownregistry.com/api/v1/blob/8718723a6f40ffb48479af421d31a3d592e1373ebe61f29566f658dc272e8c1c
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.