bug-capture SKILL.md skillA

bug-capture from rohitg00/pro-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add rohitg00/pro-workflow/bug-capture@git:20260417.f9e421e

Pins git:20260417.f9e421e in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: rohitg00/pro-workflow
Path: skills/bug-capture/SKILL.md
Versions recorded: 1
Latest version: git:20260417.f9e421e, committed Apr 17, 2026
Size: 3,436 bytes
Repository stars: 2,944
License: none declared

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".

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

# 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

The exact contents, by fingerprint

mdr add rohitg00/pro-workflow/bug-capture@sha256:280ee9587cd59a58

The line at the top of this page pins the label git:20260417.f9e421e, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_7oc6de4n7g3ydnka.svg)](https://markdownregistry.com/a/art_7oc6de4n7g3ydnka)

5 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Apr 17, 2026.

version	committed	commit	size	audit
git:20260417.f9e421e latest	2026-04-17	f9e421e	3,436 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

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

GitHub

rohitg00/pro-workflow · 2,944 stars · license none declared · pushed 2026-09-29 · 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 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.

More from rohitg00/pro-workflow

agent-teams SKILL.md skill

rohitg00/pro-workflow · skills/agent-teams/SKILL.md · Coordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and…