- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add rohitg00/pro-workflow --skill bug-capture -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add rohitg00/pro-workflow --skill bug-capture -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add rohitg00/pro-workflow --skill bug-capture -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add rohitg00/pro-workflow --skill bug-capture -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/rohitg00/pro-workflow/tree/HEAD/skills/bug-capture게시자 제공
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.
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
---name: bug-capturedescription: Capture a user-reported defect as a durable GitHub issue written in the project's own domain language…---# skills/bug-capture/SKILL.md개요
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".
FAQ
게시자에게서 skills/bug-capture/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/rohitg00/pro-workflow에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.