From pro-workflow
Captures user-reported bugs as durable GitHub issues using the project's own domain language. Avoids stale references like file paths.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pro-workflow:bug-captureThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn a conversation into an issue that still reads correctly after a
Turn a conversation into an issue that still reads correctly after a major refactor.
Let the user describe the problem in their own words. Ask at most two short clarifying questions, drawn from:
If the description already answers these, skip straight to filing. Over- interviewing is a tax the reporter pays for your uncertainty.
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.
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
whether to add a comment instead of opening a new issue. Do not silently
skip filing.
Break down when the report contains two or more independent failure modes that a different contributor could fix in parallel. Keep as one when every symptom traces to a single wrong behavior.
For a breakdown, file in dependency order so each child issue can
reference a real parent number, and mark honest Blocked by links.
Avoid inventing dependencies to make the tree look tidier.
gh issue createFile without asking the user to review the draft. Send back the URLs.
## What happened
<observed behavior, in domain terms>
## What I expected
<expected behavior>
## Reproduction
1. <step>
2. <step>
3. <step>
## Context
<anything that narrows where the bug lives, in domain terms — e.g.
"only affects the import path, not the export path">
## Parent
#<parent-number>
## What is wrong
<one behavior, narrow slice>
## What I expected
<expected for this slice>
## Reproduction
1. <step>
## Blocked by
<#issue or "none — independent">
## Context
<notes that apply only to this slice>
applyPatch() throws".After each issue, print the URL and ask whether there is a next one. Do not batch multiple reports into one filing pass — each bug deserves its own scoped issue.
npx claudepluginhub rohitg00/pro-workflow --plugin pro-workflowRuns interactive QA sessions where users describe bugs and the agent files structured GitHub issues. Explores codebase for context and domain language.
Guides conversational bug discovery and issue drafting. Listens, explores code context, assesses scope, and drafts GitHub issues with user permission.
Transforms error logs, screenshots, voice notes, and rough bug reports into structured GitHub issues with reproduction steps, impact, and evidence.