consultation-loop skillA
consultation-loop is agent-read markdown (skill) from pisberg/vibetags: Pre-push adversarial interrogation of the current branch's diff by a fresh reviewer with no memory of writing it - five scoped questions (done? production-ready? scales? secure? top risks?), answers must cite a line or admit "cannot tell from here". Advisory only, never a gate. Use when the user says "consult", "consultation loop", "are we done", "pre-push review", "interrogate this diff", or before opening a PR on substantial work..
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
# Consultation loop A voluntary pre-push interrogation of the branch diff. The reviewer must be a fresh context that did not produce the change: spawn a subagent (or a fresh `claude -p` session) and give it only the diff and the questions below. Never answer these questions from the session that wrote the code; a session reviewing its own work confirms its own assumptions. This loop is advisory. It produces ranked findings for the author to weigh, not a verdict. The blocking review is CI's job (tests, self-check, the Inquisitor); this one exists to catch what you can still fix cheaply, before the PR exists. ## Procedure 1. Compute the diff scope: `git diff origin/main...HEAD` (after `git fetch origin main`). 2. Spawn a fresh reviewer with the framing: "You did not write this code. Assume the author took shortcuts. Answer each question for this diff only. Every claim cites a file:line from the diff; if the diff cannot answer, say 'cannot tell from here' and name what evidence would answer it. Do not reassure." 3. Ask the five questions, one at a time, each with its scope clause: 1. **Are we done?** Enumerate what the task promised (the issue, the spec, the PR body …
Read the whole file at its exact version.
How to install
mdr add pisberg/vibetags/consultation-loop@git:20260815.32e6c75mdr add pisberg/vibetags/consultation-loop@sha256:126be3f61f79bfbaPin 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_trn2vw2yzwg64yr2)
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 (3433 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_trn2vw2yzwg64yr2 GET https://markdownregistry.com/api/v1/resolve?ref=pisberg/vibetags/consultation-loop GET https://markdownregistry.com/api/v1/blob/126be3f61f79bfbae7a713252547a463c4f195a2f0d2ad250774a3c56ac0de3c
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.