skills.rest
SwitchbackTech
SwitchbackTechOFFICIAL
Explore all skills by this author →
𝕏@CompassCalendarGitHub

bug-capture

Convert user bug reports into detailed GitHub issues with evidence and diagnosis.

228|68|Updated Sep 27, 2023
Search Tags:#github#evidence#diagnosis#reproduction-steps#bug#issue-generation
One-click install
npx skills add https://github.com/SwitchbackTech/compass-calendar --skill bug-capture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-capture
Source: https://github.com/SwitchbackTech/compass-calendar/tree/main/.agents/skills/bug-capture
Command: npx skills add https://github.com/SwitchbackTech/compass-calendar --skill bug-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture a real bug as a GitHub issue with enough evidence for a later agent to fix it quickly: workflow, screenshot evidence, diagnosis, likely fix, and verification path.

Core Features & Use Cases

  • Gather reporter context (description, reproduction steps, environment state, logs, and attached screenshots) and translate it into a structured GitHub issue.
  • Diagnose and summarize the problem without altering product code, including confidence levels and reproduction status.
  • Publish a high-context issue with workflow details, evidence, diagnosis, a likely fix, and a verification path for QA and engineering teams.

Quick Start

Draft a GitHub issue from a bug report by providing evidence, context, reproduction steps, and a proposed fix.

Frequently Asked Questions about bug-capture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn bug reports into high-context GitHub issues?▼

To generate GitHub issues from bug reports, provide reporter context, reproduction steps, environment state, and logs. The skill translates this input into a structured issue featuring diagnosis, a likely fix, and a verification path.

What evidence is needed to create a reproducible bug issue for software engineering?▼

Generating a reproducible bug issue requires gathering evidence like screenshots, logs, reproduction steps, and environment state. This high-context information enables accurate diagnosis and establishes a clear verification path for engineering teams.

Can I use bug reports from customer support channels to generate GitHub issues?▼

Yes, you can process bug reports from customer support channels to generate GitHub issues. The skill collects descriptions and environment state from these channels to produce high-context issues for QA and engineering workflows.

Does generating a GitHub issue from a bug report alter product code?▼

Generating a GitHub issue from a bug report does not alter product code. It strictly diagnoses and summarizes the problem, including confidence levels and reproduction status, to prepare a high-context issue for later resolution.

What is the best way to document reproduction steps and diagnosis for a GitHub issue?▼

The best way to document reproduction steps and diagnosis is to articulate the reproducible bug into a structured format. This includes evidence collection, environment state, likely fix, and verification path within the GitHub issue.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
EmasoftEmasoft
13

amoa-two-phase-mode

Coordinate plan-then-execute workflows with GitHub issues, YAML state files, and verification polls.

Community
Advanced
yash-gargyash-garg

qa

Convert conversational bug reports into structured GitHub issues.

Community
Advanced
liumeixinliumeixin
4

dogfood

Automate exploratory QA testing of web applications with browser tools.

Community
Advanced