issue-report-generator

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.

1.05x

Quality

81%

Does it follow best practices?

Impact

98%

1.05x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized with strong worked examples and a clear, sequenced workflow supported by a checklist and an appropriately separated reference file. Its main weakness is verbosity: the early analysis steps over-elaborate concepts Claude already knows.

Suggestions

Collapse the nested bullets in Steps 1–3 into compact checklists, dropping obvious sub-prompts like 'What is the expected behavior?' and 'Extract file paths / class names / line numbers' that Claude already knows to do.

Add an explicit validation feedback loop before finalizing (e.g. 'Review the report against the Quality Checklist; if any section is missing or vague, revise before posting') to push workflow clarity toward the top anchor.

Move the four full worked examples (or the MUST/MUST NOT constraints) into report_patterns.md and summarize them inline, keeping SKILL.md a leaner overview pointing to the reference.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and well-structured, but Steps 1–3 rely on extensive nested bullets restating obvious analysis sub-steps (e.g. 'Extract file paths', 'Extract class/method names', 'What is the expected behavior?') that Claude already knows, which is noticeable padding.	3 / 5
Actionability	Four full worked report examples (NPE, assertion, timeout, integration) plus a template-selection table and a concrete report-structure spec provide mostly copy-paste-ready guidance, with only minor gaps in executable instruction for the analysis steps.	4 / 5
Workflow Clarity	A clear 5-step sequence with a final Quality Checklist acting as a validation checkpoint; no explicit validate-then-fix feedback loop, but report generation is not a destructive/batch operation so the cap does not apply.	4 / 5
Progressive Disclosure	Well-organized sections with a clearly signaled, one-level-deep reference to references/report_patterns.md (verified to exist) that holds the comprehensive templates; only minor organization gaps keep it below the top anchor.	4 / 5
	Total	15 / 20 Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that explicitly states concrete capabilities and provides explicit, natural-language trigger phrases. Its only weakness is the somewhat broad 'debugging issues' trigger, which slightly raises conflict risk with general debugging skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'generate clear, actionable issue reports', 'Analyze test failures to understand expected vs. actual behavior', 'identify affected code components', and 'produce well-structured Markdown reports suitable for GitHub Issues' — giving comprehensive coverage of capabilities.	5 / 5
Completeness	Clearly answers both what (generate issue reports from failing tests, analyze failures, identify affected code) and when (explicit 'Use when...' triggers with concrete phrases), matching the top anchor.	5 / 5
Trigger Term Quality	The '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' clause covers comprehensive natural phrases and synonyms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	The 'failing tests' / 'GitHub Issues' / 'bug report' niche is distinct, but the broad 'when debugging issues' trigger creates minor overlap risk with general debugging skills, so it sits just below the top anchor.	4 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ArabelaTso/Skills-4-SE
Path: skills/issue-report-generator/SKILL.md
Commit: 4f38503

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.