AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Verify Bug Reports

skill-stumason-skills-verify-bug-reports · by StuMason

Never take bug reports or QA feedback as gospel. Use before fixing anything QA or a user reported, to verify what correct behaviour actually is.

↗ Repository
— No reviews yet
0 installs
6 views
0.0% view→install

Install

$ agentstack add skill-stumason-skills-verify-bug-reports

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-stumason-skills-verify-bug-reports)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 23d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Verify Bug Reports? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Verify Bug Reports

QA describes what they see. They do not define what is correct. A "fix" for a misunderstood requirement is a new bug with a paper trail, so before fixing what is reported, verify the report.

The check

  1. Reproduce what they saw. If you cannot reproduce it, that is your finding, go back with exactly what you tried.
  2. Find the source of truth for expected behaviour. The ticket, the spec, an ADR, how the rest of the codebase handles the same pattern. Not the bug report itself, and not vibes.
  3. Deliver a verdict, one of three:
  • The report is right. Behaviour contradicts the source of truth. Fix it.
  • The report misunderstands the requirement. The observed behaviour is correct. Explain why, with the source cited. Do not "fix" it. Do not change working code to match a misreading.
  • Nobody actually knows what correct is. There is no source of truth to check against. That is not a bug, that is an unwritten requirement: stop and get it decided before touching code (see the ticket-readiness skill).

Why bother

Because "QA said so" is how correct code gets broken politely. The reporter is describing a symptom through their own model of the system, and their model may be wrong. Asking "hang on, is that actually the intended behaviour?" costs nothing. Being the agent who quietly broke checkout because a tester misread the spec costs rather more.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills