agentsclimarketplace

Prod bug report

Skill press-pass/gifhub/skills/prod-bug-report

Walk real production user flows like a user, find bugs, and write each one up as a reproducible bug report (steps / expected behavior / actual behavior). Report-only — no code changes, no fixes, no PRs to the app.From its SKILL.md

Install
npx -y skills add press-pass/gifhub --skill prod-bug-report

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, as published. Nobody here has run it

prod-bug-report

Exercise the app's production user flows end to end, like a real person, and write up every bug you hit as a structured, reproducible report.

This is report-only. You do not fix anything, change the app, or open code PRs — you produce bug reports.

Run it safely (this is production)

You're touching the live app and real infrastructure. Be a good citizen:

  • Prefer read-mostly paths. Avoid destructive or irreversible actions (deletes, payments, sending real emails/notifications, state changes that other users would see) unless you've been explicitly cleared to.
  • Use a dedicated test account — never act on real users' data.
  • Don't spam: minimal repetitions, and clean up any test data you create.
  • If a step would charge money, notify real people, or mutate shared/other-user data, stop and note it in the report instead of doing it.

What to exercise

Walk the full set of production flows like both a first-time and a returning user: sign up / log in, the core features, settings and configuration, navigation, empty states, error states, and the obvious edge cases. Drive it through a real browser and watch for: broken UI, wrong data or numbers, dead buttons, console/network errors, misleading or confusing messaging, and anything that wouldn't match a reasonable user's expectation.

Bug report format (use exactly this)

For every bug, write a report in this format:

steps:
1. starting at the homepage, do the thing step 1
2. do the thing step 2
3. do the thing step 3

expected behavior: what should have happened
actual behavior: what actually happened

Rules for good reports:

  • Steps always start from the homepage and are concrete enough that anyone can follow them to reproduce — name the exact buttons, fields, and links, and the exact input you used.
  • Keep steps minimal: the shortest path that triggers the bug.
  • expected behavior and actual behavior are one line each, specific and observable.
  • One report per bug. When filing several, put a short title line above each.
  • Attach a screenshot or short clip when it helps a non-technical reader see it.

Output

Collect the reports in reports/<date>-prod-bugs.md (one file, all bugs), or file each as a GitHub issue if the team uses issues. Lead with a one-line summary: how many flows you exercised and how many bugs you found.

Keep looking

Skills are one crate of 608,475. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.