report-bug

Name: report-bug
Availability: InStock
Author: TalonT

Investigate bugs from error context and write a structured markdown report.

5|1|Updated Feb 18, 2026

Search Tags:#debugging #troubleshooting #bug report #error analysis #code investigation #fingerprint

Ready to run

npx skills add https://github.com/TalonT-Org/AutoSkillit --skill report-bug-talont-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: report-bug
Source: https://github.com/TalonT-Org/AutoSkillit/tree/main/src/autoskillit/skills/report-bug
Command: npx skills add https://github.com/TalonT-Org/AutoSkillit --skill report-bug-talont-org

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of investigating bugs based on provided error messages and generating a structured report, streamlining the debugging workflow.

Core Features & Use Cases

Targeted Bug Investigation: Analyzes error context to pinpoint the root cause of issues.
Structured Reporting: Creates a markdown report detailing the error, hypothesis, and recommended actions.
Fingerprint Generation: Outputs a deduplication fingerprint for bug tracking systems.
Use Case: When a test fails with an obscure error message, this skill can quickly analyze the traceback, identify the faulty code section, and generate a report to guide the developer.

Quick Start

Use the report-bug skill to investigate the provided error context and write a report to /tmp/bug_report.md.

Frequently Asked Questions about report-bug

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

FAQPage Schema

How do I automatically generate a bug report from an error traceback?▼

To generate a bug report from a traceback, provide the error context to the skill. It investigates the codebase using targeted searches to pinpoint the source and writes a structured markdown report detailing the error and recommended actions.

How can I deduplicate bug reports in a continuous integration pipeline?▼

To deduplicate bug reports in a pipeline, the skill outputs a unique deduplication fingerprint for each investigated error. This lightweight process avoids spawning subagents, ensuring fast, non-blocking execution for tracking systems.

What is the best way to investigate obscure error messages in a codebase?▼

The best way to investigate obscure errors is to use targeted codebase searches with tools like Grep and Read. This identifies the faulty code sections and generates a hypothesis detailing the error source and recommended actions.

Does this bug investigation approach spawn subagents during code analysis?▼

No, this bug investigation approach does not spawn subagents. It is designed to be a lightweight skill that performs targeted code searches directly, ensuring fast execution suitable for non-blocking pipeline integration.

When do I need to write a structured markdown report for a failing test?▼

You need to write a structured markdown report when a test fails with an obscure error. The skill analyzes the traceback, identifies the faulty code section, and outputs a report to a specified path like /tmp/bug_report.md to guide debugging.

Can I use Grep and Read commands for error analysis and bug tracking?▼

Yes, you can use Grep and Read commands for error analysis. The skill utilizes these tools to perform targeted codebase searches, identifying error sources and generating a structured markdown report with a deduplication fingerprint.