bug-capture skillA
bug-capture is agent-read markdown (skill) from rohitg00/pro-workflow: Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug", "capture this"..
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
# bug-capture Turn a conversation into an issue that still reads correctly after a major refactor. ## Flow ### 1. Listen, then clarify minimally Let the user describe the problem in their own words. Ask at most two short clarifying questions, drawn from: - Expected behavior vs. actual behavior. - Concrete reproduction steps if not already implied. - Frequency: deterministic, intermittent, or one-off. If the description already answers these, skip straight to filing. Over- interviewing is a tax the reporter pays for your uncertainty. ### 2. Explore in parallel While the user is answering, start a background exploration of the relevant area. The goal is **not** to propose a fix. The goal is to absorb the project's own vocabulary — the nouns and verbs the codebase uses for this feature — so the issue reads like it was written by a maintainer. If the repo has a glossary file (common names: GLOSSARY.md, UBIQUITOUS_LANGUAGE.md, docs/domain.md), read it first. ### 3. Check for duplicates before filing Run `gh issue list --search "<key phrase>" --state all --limit 10`. If a live or recently closed issue matches, surface it to the user and ask …
Read the whole file at its exact version.
How to install
mdr add rohitg00/pro-workflow/bug-capture@git:20260417.f9e421emdr add rohitg00/pro-workflow/bug-capture@sha256:280ee9587cd59a58Pin 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_7oc6de4n7g3ydnka)
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 (3436 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
rohitg00/pro-workflow · 2,879 stars · license none · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7oc6de4n7g3ydnka GET https://markdownregistry.com/api/v1/resolve?ref=rohitg00/pro-workflow/bug-capture GET https://markdownregistry.com/api/v1/blob/280ee9587cd59a5831d637a210b6e3287178ecdd782f6267ffa12040b4de14df
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.
More from rohitg00/pro-workflow
Every file in rohitg00/pro-workflow