Does this replace external tools like Jira or GitHub Issues?

While it can function as a standalone internal tracker, it is primarily designed to provide high-quality, code-centric documentation that can be used to populate any project management tool.

Can the skill update the status of an existing bug?

Yes, it follows a file-naming convention that allows you to transition bugs between OPEN, FIXED, and REJECTED statuses.

How does this skill investigate bugs?

It launches an 'Explore' subagent using Claude Opus to analyze code paths, related systems, and existing comments to find the technical root cause before writing the report.

Where are the bug reports stored?

Reports are automatically saved as standardized markdown files within the project's DevPlans/Bugs/ directory.

What information is included in the AI-generated reports?

Each report includes a technical summary, symptoms, root cause analysis, affected code (files and lines), potential solutions, and priority levels.

Automated Bug Reporting

Name: Automated Bug Reporting
Author: faughnn

byfaughnn

Security & Testing

Automates technical bug investigation and generates standardized markdown reports using AI subagents.

About

This skill streamlines the debugging workflow by deploying an 'Explore' subagent to perform deep-dive investigations into code paths and root causes before a report is ever written. It ensures project consistency by automatically generating structured markdown files in the DevPlans/Bugs/ directory, complete with technical analysis, affected file paths, and potential solutions. By leveraging Claude Opus for the investigation phase, it transforms vague symptoms into actionable developer documentation with clear status tracking and priority levels.

Key Features

Standardized markdown report generation with technical specifications
0 GitHub stars
Identification of affected code paths and specific line numbers
Automated 'Explore' subagent for deep-code root cause analysis
Integrated status management (OPEN, FIXED, REJECTED) via file naming
Structured solution mapping and priority assessment

Use Cases

Converting user-reported symptoms into technical root-cause documentation
Performing deep-dive investigations into complex logic errors across multiple systems
Maintaining a standardized, version-controlled bug tracking system within a repository

About

Key Features

Standardized markdown report generation with technical specifications
0 GitHub stars
Identification of affected code paths and specific line numbers
Automated 'Explore' subagent for deep-code root cause analysis
Integrated status management (OPEN, FIXED, REJECTED) via file naming
Structured solution mapping and priority assessment

Use Cases

Converting user-reported symptoms into technical root-cause documentation
Performing deep-dive investigations into complex logic errors across multiple systems
Maintaining a standardized, version-controlled bug tracking system within a repository