draft-bug

Name: draft-bug
Availability: InStock
Author: gautam-achieveai

Write bug reports with root cause analysis and regression tests.

2|Updated Apr 12, 2026

Search Tags:#code analysis #root cause analysis #issue tracking #regression testing #bug reporting

Ready to run

npx skills add https://github.com/gautam-achieveai/ClaudePlugins --skill draft-bug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: draft-bug
Source: https://github.com/gautam-achieveai/ClaudePlugins/tree/main/development/skills/draft-bug
Command: npx skills add https://github.com/gautam-achieveai/ClaudePlugins --skill draft-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of writing detailed and reproducible bug reports, ensuring that defects are thoroughly investigated and documented.

Core Features & Use Cases

Evidence-Gathering: Collects and analyzes code and log evidence to establish the problem.
Root Cause Hypothesis: Investigates multiple root causes in parallel with subagents.
Regression Testing: Validates hypotheses with scratch regression tests.
Blind-Spot Scan: Identifies related issues and risks.
Composed Bug Write-Up: Generates a comprehensive bug report with repro steps and root cause.

Quick Start

Use the draft-bug skill to create a bug report for a reported issue.

Frequently Asked Questions about draft-bug

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

FAQPage Schema

How do I write a bug report with root cause analysis and reproducible steps?▼

You can create a bug report with root cause analysis by gathering code evidence, testing multiple root cause hypotheses in parallel using subagents, and validating them with scratch regression tests to ensure reproducibility.

What is evidence-based bug reporting and how does it work?▼

Evidence-based bug reporting is the process of collecting and analyzing code and log evidence to establish a problem, investigating multiple root causes in parallel with subagents, and validating hypotheses with scratch regression tests. It also includes a blind-spot scan to identify related issues and risks.

Do I need codebase access and the ability to run tests for issue tracking?▼

Yes, codebase access and the ability to run tests are required for issue tracking and bug reporting. This environment allows the system to execute scratch regression tests to validate root cause hypotheses and generate a comprehensive bug write-up with reproducible steps.

What's the best way to investigate multiple root causes for a code defect?▼

The best way to investigate multiple root causes for a code defect is using parallel subagent investigation. This method tests multiple root cause hypotheses simultaneously, validates them with scratch regression tests, and performs a blind-spot scan to identify related issues and risks.

How do regression tests validate a root cause hypothesis during code analysis?▼

Regression tests validate a root cause hypothesis during code analysis by serving as scratch tests that reproduce the defect. Running these tests against the codebase confirms or rejects the investigated root causes, ensuring the final bug report contains verified, reproducible regression tests.

When should I perform a blind-spot scan during root cause analysis?▼

You should perform a blind-spot scan during root cause analysis after gathering initial evidence and testing hypotheses. This scan identifies related issues and risks surrounding the primary defect, ensuring the final bug report provides comprehensive coverage of potential regressions.