bug-reproduction-test-generator
Automatically generates executable tests that reproduce reported bugs from issue reports and code repositories. Use when users need to: (1) Create a test that reproduces a bug described in an issue report, (2) Generate failing tests from bug descriptions, stack traces, or error messages, (3) Validate bug reports by creating reproducible test cases, (4) Convert issue reports into executable regression tests. Takes a repository and issue report as input and produces test code that reliably triggers the reported bug.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill bug-reproduction-test-generator90
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
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates a specific capability (generating tests from bug reports), provides comprehensive trigger terms that developers would naturally use, and explicitly states when to use it with four distinct scenarios. The description is well-structured, uses proper third-person voice, and includes helpful context about inputs and outputs.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'generates executable tests', 'reproduce reported bugs', 'create failing tests from bug descriptions, stack traces, or error messages', 'convert issue reports into executable regression tests'. Also specifies inputs (repository and issue report) and outputs (test code). | 3 / 3 |
Completeness | Clearly answers both what ('generates executable tests that reproduce reported bugs') and when with explicit 'Use when users need to:' clause followed by four specific trigger scenarios. The final sentence also clarifies inputs and outputs. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'bug', 'issue report', 'reproduce', 'test', 'stack traces', 'error messages', 'regression tests', 'failing tests', 'bug descriptions'. These are terms developers naturally use when dealing with bug reproduction. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on bug reproduction via test generation from issue reports. The combination of 'issue reports', 'bug reproduction', and 'test generation' creates a distinct trigger profile unlikely to conflict with general testing or debugging skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability and clear workflow guidance. The executable examples across multiple languages are excellent. However, it's somewhat verbose with tips and guidance that Claude already knows, and the content could be better organized with progressive disclosure to separate reference material from core workflow.
Suggestions
Move language-specific patterns to a separate PATTERNS.md file and reference it from the main skill
Remove or significantly condense the 'Tips for Effective Reproduction Tests' section - these are general testing principles Claude already knows
Trim the 'Handling Underspecified Issues' section to just the example, as the numbered list restates obvious practices
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanation. Sections like 'Handling Underspecified Issues' and 'Tips for Effective Reproduction Tests' contain guidance Claude likely already knows. The language-specific patterns section adds value but could be more compact. | 2 / 3 |
Actionability | Provides fully executable code examples across multiple languages (Python/pytest, Java/JUnit, JavaScript/Jest). The example workflow shows complete input-to-output transformation with copy-paste ready test code and clear assertions. | 3 / 3 |
Workflow Clarity | Clear 4-step workflow with explicit sequencing (Analyze → Inspect → Generate → Output). Each step has specific sub-tasks. The example workflow demonstrates the complete process with validation through running the test to confirm reproduction. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~180 lines) that could benefit from splitting language-specific patterns into separate reference files. No external file references are provided for advanced topics. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
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.