skills.rest
ArabelaTso
ArabelaTsoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

issue-report-generator

Generate structured Markdown issue reports from failing test cases.

142|14|Updated Feb 14, 2026
Search Tags:#code analysis#debugging#markdown#bug report#test failure#issue generation
One-click install
npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill issue-report-generator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-report-generator
Source: https://github.com/ArabelaTso/Skills-4-SE/tree/main/skills/issue-report-generator
Command: npx skills add https://github.com/ArabelaTso/Skills-4-SE --skill issue-report-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of clear, detailed issue reports from failing tests, saving developers time and ensuring consistent bug documentation.

Core Features & Use Cases

  • Automated Report Generation: Creates structured Markdown reports from test failures, including exceptions, assertion errors, and timeouts.
  • Root Cause Analysis Assistance: Helps identify affected code components and suggests potential root causes.
  • Use Case: When a test fails unexpectedly, use this Skill to automatically generate a comprehensive bug report that includes steps to reproduce, expected vs. actual behavior, and affected code, ready to be posted to a bug tracker.

Quick Start

Use the issue-report-generator skill to create a bug report from the provided test failure details.

Frequently Asked Questions about issue-report-generator

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

FAQPage Schema
How do I generate a bug report from a failing test case?▼

To generate a bug report from a failing test case, you can use an issue report generator that analyzes test failures, identifies affected code components, and outputs a structured Markdown report ready for issue tracking systems.

What is automated issue generation from test failures?▼

Automated issue generation from test failures is the process of analyzing exceptions, assertion errors, and timeouts to infer root causes and produce structured Markdown documentation for bug trackers.

Can I automatically identify root causes and affected code from assertion errors?▼

Yes, you can automatically identify root causes and affected code from assertion errors by analyzing the test failure details and repository code to infer the underlying components causing the bug.

Does the issue report generator output Markdown for issue tracking systems?▼

Yes, the issue report generator outputs structured Markdown that includes steps to reproduce, expected versus actual behavior, and affected code, making it ready to post directly to issue tracking systems.

What is the best way to document debugging steps for unexpected test timeouts?▼

The best way to document debugging steps for unexpected test timeouts is to automatically generate a comprehensive Markdown report detailing the timeout, affected code, and inferred root causes for consistent documentation.

Do I need to manually write reproduction steps when documenting a bug?▼

No, you do not need to manually write reproduction steps when documenting a bug, as the report generation process automatically extracts test failure details and constructs the expected versus actual behavior for you.

Related Skills

Explore More Software Engineering Skills→
POWERFULMOVESPOWERFULMOVES
1

test-fixing

Group and fix failing software tests by prioritizing error types.

Community
Advanced
danieljformandanieljforman

ceos-ids

Identify root causes and assign owner To-Dos with due dates.

Community
Advanced
a-ariffa-ariff
14

root-cause-tracing

Trace bugs backward from symptoms to identify root causes.

Community
Intermediate
TumeloRamaphosaTumeloRamaphosa

investigate

Investigate software failures through a four-phase evidence-first root-cause workflow.

Community
Advanced