bug-capture

仓库创建 2026年2月2日最近提交 1 天前SkillHot 收录 22 天前

▸ 精选理由

能生成不依赖具体路径的长期可读问题描述，便于维护。

▸ 风险提示

会浏览仓库代码以获取上下文

这个 Skill 做什么

把对话或 QA 转化为项目术语的可持续 GitHub Issue。

把用户口述的问题整理成项目内部语境能读懂的 GitHub Issue，附上复现步骤和必要背景，但不会泄露具体文件路径或行号。遇到用户说“报 bug”或 QA 发现问题就用，最多问一两句澄清以保证可复现性。输出耐得住重构的、便于开发直接处理的 issue 模板，便于跟踪和修复。

▸ 展开 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".

开发编程错误捕获自动写 issue代码上下文Claude Code

2.7k

Stars

263

Forks

仓库内 Skill

+73

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/rohitg00/pro-workflow/main/skills/bug-capture/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/rohitg00/pro-workflow/main/skills/bug-capture/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# 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 go

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有