bug-report
Write a clear, reproducible bug report that gets fixed fast. Use when asked to write a bug report, file a defect, report an issue, or turn 'it's broken' into an actionable ticket. Produces a structured report — a precise title, steps to reproduce, expected vs. actual, environment, severity/priority, and evidence — so a developer can reproduce and fix it without a back-and-forth.
npx skills add mohitagw15856/pm-claude-skills --skill bug-report --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Bug Report Skill A bug report is only useful if someone else can **reproduce** it. The best ones are precise: an exact title, numbered steps, what you expected vs. what happened, and the environment it happened in. This skill turns a vague "it's broken" into a ticket a developer can act on immediately — no clarifying round-trips. ## Working from a brief Given "the export button doesn't work", **write the full report anyway** — infer the likely repro steps, expected behaviour, and environment, marking inferences *(confirm)*. Keep facts (what was observed) separate from guesses (likely cause). Never invent logs/errors; flag them to attach. ## Required Inputs Ask for these only if they aren't already provided (else infer and label): - **What's wrong** — what you did, what happened, and what you expected instead. - **Steps to reproduce** — the exact sequence (and whether it's consistent or intermittent). - **Environment** — device, OS, browser/app version, account/role, and any relevant data state. - **Evidence** — screenshots, a screen recording, console/network errors, logs, request IDs. ## Output Format ### Bug Report - **Title** — a precise one-liner: what's broken + where + the
- Working from a brief
- Required Inputs
- Output Format
- Bug Report
- Quality Checks
- Anti-Patterns
- Based On
What does the bug-report skill do?
Write a clear, reproducible bug report that gets fixed fast. Use when asked to write a bug report, file a defect, report an issue, or turn 'it's broken' into an actionable ticket. Produces a structured report — a precise title, steps to reproduce, expected vs. actual, environment, severity/priority, and evidence — so a developer can reproduce and fix it without a back-and-forth.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill bug-report --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.