- 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".
常見問題
從發布者下載 skills/bug-capture/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/rohitg00/pro-workflow。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。