Automatically generate clear, actionable issue reports from failing tests and repository analysis. Analyze test failures to understand expected vs. actual behavior, identify affected code components, and produce well-structured Markdown reports suitable for GitHub Issues or similar trackers. Use when a test fails, when debugging issues, or when the user asks to create an issue report, generate a bug report, or document a test failure.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill issue-report-generator80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Exception-based issue report generation
Title format: exception in component
30%
100%
Title length
100%
100%
All required sections present
100%
100%
Exact error message used
100%
100%
Stack trace included
100%
100%
Affected code: file, method, line
100%
100%
Null variable identified
100%
100%
Uncertainty language used
100%
100%
Markdown code blocks
100%
100%
Test details included
100%
100%
No vague language
100%
100%
No judgmental language
100%
100%
Reproduction steps
100%
100%
Without context: $0.1155 · 34s · 8 turns · 13 in / 2,008 out tokens
With context: $0.3971 · 1m 8s · 15 turns · 19 in / 3,366 out tokens
Assertion failure issue report with template selection
Title format: feature returns incorrect result
100%
100%
Title length
0%
100%
All required sections present
70%
100%
Expected vs actual values shown
100%
100%
Assertion failure quoted
100%
100%
Affected code: file, method, line
100%
100%
Wrong value source identified
100%
100%
Evidence-based only
100%
100%
Markdown code blocks
100%
100%
Test details included
100%
100%
Reproduction steps
100%
100%
No vague language
100%
100%
No judgmental language
100%
100%
Without context: $0.1129 · 37s · 9 turns · 12 in / 2,088 out tokens
With context: $0.2907 · 51s · 11 turns · 198 in / 2,692 out tokens
Performance timeout issue report with suggested fix
Title format: performance/timeout
100%
100%
Title length
60%
0%
All required sections present
70%
100%
Slow operation identified
100%
100%
Algorithmic complexity noted
100%
100%
Input size mentioned
100%
100%
Timeout duration stated
100%
100%
Affected code: file, method, lines
100%
100%
Uncertainty language used
100%
100%
Suggested fix or investigation
100%
100%
Markdown code blocks
100%
100%
Test details included
100%
100%
No vague language
100%
100%
No judgmental language
100%
100%
Without context: $0.1483 · 49s · 8 turns · 13 in / 2,419 out tokens
With context: $0.3468 · 1m 2s · 14 turns · 6,416 in / 2,808 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.