bug-reproduction-brief
Turn a vague, intermittent, or environment-specific bug report into a minimal evidence-backed reproduction before proposing a fix.
Install / Use
npx skills add github/awesome-copilot --skill bug-reproduction-briefInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of bug-reproduction-brief
bug-reproduction-brief scores 93/100 on our quality scale, 587th of 4,698 Development & Engineering skills we index (top 13%).
Its SKILL.md is 2.9 KB long, well organised into 12 sections with 3 code examples: a solid amount of guidance for an agent.
With 39,348 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so bug-reproduction-brief is actively maintained.
- Our last check on 2026-10-03 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
bug-reproduction-brief compared with similar skills
All 4 of these similar skills score higher than bug-reproduction-brief; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| bug-reproduction-brief (this skill)by github | 93 | 39.3k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install bug-reproduction-brief?
- Run
npx skills add github/awesome-copilot --skill bug-reproduction-brief. The install tabs above show the steps for each supported agent. - Which AI agents does bug-reproduction-brief work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is bug-reproduction-brief safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is bug-reproduction-brief still maintained?
- The repository was last updated about 2 months ago, so bug-reproduction-brief is actively maintained.
Skill content
View source on GitHubname: bug-reproduction-brief description: 'Turn a vague, intermittent, or environment-specific bug report into a minimal evidence-backed reproduction before proposing a fix.'
Bug Reproduction Brief
Use this skill when a bug report is incomplete, intermittent, environment-specific, or mixed with an assumed cause. The goal is to prove the smallest observable failure before diagnosis or repair begins.
1. Record the observed failure
Capture the exact error, incorrect output, timestamp, affected route or command, and the smallest known input. Preserve relevant logs without secrets or personal data. Label second-hand descriptions as unverified.
2. Identify the environment
Record only facts you can inspect:
- repository and commit;
- runtime and package-manager versions;
- operating system or container;
- dependency lockfile;
- relevant feature flags;
- whether the target is local, test, staging, or production.
Never guess credentials or production configuration.
3. Separate expected from actual behaviour
Write two explicit observable statements:
Expected: [observable result]
Actual: [observable result, including status or error]
Do not put the suspected cause in either statement.
4. Reduce the reproduction
Start from the reported path, then remove unrelated data, services, and steps one at a time. Keep the smallest fixture that still fails. If the failure stops, restore the last removed condition and record it.
Prefer an isolated test, minimal script, or smallest safe request over reproducing against production.
5. Prove repeatability
Run the minimal reproduction at least twice where safe. Record commands and outputs. If the failure is intermittent, report the observed frequency and duration instead of calling it deterministic.
6. Stop before repair
A verified reproduction is the deliverable. Do not edit implementation code while building the brief because that can destroy the evidence or mix diagnosis with remediation.
Output
# Bug Reproduction Brief
- Target and commit:
- Environment:
- Expected:
- Actual:
- Minimal steps:
- Minimal fixture:
- Reproduced: yes / no / intermittent
- Evidence:
- Unknowns:
- Safe next hypothesis to test:
Safety boundaries
- Do not change production data merely to reproduce a bug.
- Do not publish secrets, customer records, or private source.
- Do not claim a root cause from correlation alone.
- Use read-only or reversible discovery first.
- Stop after a verified reproduction; diagnosis and repair are separate workflows.
Example prompt
Use the Bug Reproduction Brief skill on the failing checkout test. Do not fix it yet. Reduce it to the smallest safe failing fixture and report the exact command evidence, expected result, actual result, and remaining unknowns.
Source and licence
Adapted from the MIT-licensed workflow at https://github.com/skyestrela/ai-agent-skill-preview.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
