naodeng/awesome-qa-skills96 installs

bug-reporting

Q: How do I install this agent skill?

Run npx skills add https://github.com/naodeng/awesome-qa-skills --skill bug-reporting.

Q: Is this agent skill safe to install?

Review the displayed partner audits, complete source, permissions, dependencies, and exact revision before installing.

Use this skill when you need to write clear, reproducible bug reports with steps, environment details, and evidence; triggers include bug reporting and defect reporting.

How do I install this agent skill?

npx skills add https://github.com/naodeng/awesome-qa-skills --skill bug-reporting

view source ↗

Is this agent skill safe to install?

Gen Agent Trust Hubpass
The skill is generally safe, focusing on bug report generation and format conversion. It includes local Python scripts for converting reports between Markdown, JSON, CSV, and other formats. Security findings are minor, involving the use of subprocess for local script execution and the processing of external bug reports which presents a surface for indirect prompt injection.
Socketpass
No alerts
Snykpass
Risk: LOW · No issues
Runlayerpass
1/6 files flagged

What does this agent skill do?

Bug Reporting

Chinese version： See the corresponding Chinese skill.

When to Use

Need help with bug reporting in a real project context.
Need an output that can be used directly for execution, review, or follow-up.

Workflow

Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable.
If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps.
Default to Markdown; switch formats only when the user asks.

Core Constraints

Prioritize by risk / business impact — do not treat everything equally.
Separate confirmed facts from current assumptions.
Do not invent endpoints, fields, environments, or root causes the user did not provide.
Keep output executable: concrete scenarios, clear priority, clear next steps.

Progressive Disclosure

Before producing output, read and follow prompts/bug-reporting.md (minimum coverage, output structure, quality bar).
When Excel/CSV/JSON/Word is requested: read output-formats.md and honor the format.
When a ready-made template fits: use matching files under output-templates/.
For deep framework/troubleshoot/schema notes: read only the relevant file(s) under references/, do not load the whole directory.
For format conversion or helper checks: prefer existing scripts/ over reinventing.
For evaluating/regressing this skill: use evals/ with skill-up.

Pre-delivery Checklist

Followed the main prompt's output structure
Minimum coverage focus: title, environment, preconditions, repro steps, actual result, expected result, repro frequency, impact scope, ... (details in main prompt)
Covered the minimum checklist, or explained omissions
High-risk items have explicit priority
Did not invent details the user did not provide
Assumptions and gaps are marked

Common Pitfalls

Do not pretend completeness when scope/context is missing.
Do not treat every item as equally important.
Do not skip assumptions and information gaps.
Do not dump generic theory unrelated to the current toolchain.

How can the creator link this skill?

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/naodeng/awesome-qa-skills/bug-reporting">View bug-reporting on skillZs</a>