Download for MacApple silicon, macOS 14+
Skill

bug-capture

@rohitg00 Updated 2026-07-27

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

agent-orchestrationai-agentsai-codingai-workflowclaudeclaude-codeclaude-code-pluginclaude-code-skills

Install

With your agent

Install OMGSkills skill "rohitg00/pro-workflow:skills/bug-capture" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/rohitg00/pro-workflow /tmp/pro-workflow && ln -s /tmp/pro-workflow/skills/bug-capture ~/.claude/skills/bug-capture

From README

bug-capture Turn a conversation into an issue that still reads correctly after a major refactor. Flow 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. 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, UBIQUITOUSLANGUAGE.md, docs/domain.md), read it first.