skills.rest
abdullah72005
abdullah72005COMMUNITY
Explore all skills by this author →
GitHub

qa

Files durable GitHub issues from conversational bug reports during interactive QA sessions.

1|Updated Jun 15, 2026
Search Tags:#testing#qa#bug report#github issues#gh cli#issue triage#reproduction steps
One-click install
npx skills add https://github.com/abdullah72005/skills --skill qa-abdullah72005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/abdullah72005/skills/tree/main/qa/.agents/skills/qa
Command: npx skills add https://github.com/abdullah72005/skills --skill qa-abdullah72005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reporting bugs well is hard: users describe problems loosely, and issues often end up tied to fragile implementation details that go stale after refactors. This Skill turns a casual conversation about problems into well-structured, durable GitHub issues without burdening the user. ## Core Features & Use Cases - Conversational issue intake: Users describe bugs in their own words with at most 2-3 short clarifying questions, avoiding over-interviewing. - Background codebase exploration: An Explore agent learns the project's domain language and expected behavior so issues read naturally without citing files or line numbers. - Smart issue breakdown: Decides whether a report is one issue or several thin, parallelizable issues, filing them in dependency order with honest blocking relationships. - Use Case: During a QA session, a user says the form validation is wrong and the redirect is broken. The Skill files two independent GitHub issues with reproduction steps, marks them as unblocked, and shares the URLs. ## Quick Start Start a QA session and file GitHub issues for the bugs I describe.

Frequently Asked Questions about qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I file GitHub issues from a conversation?▼

Describe the problem in your own words during the QA session. The agent asks at most 2-3 clarifying questions, explores the codebase for context, then files the issue with gh issue create and shares the URL without requiring review.

How to write bug reports that survive code refactors?▼

Write issues from the user's perspective describing behaviors, not code. Avoid file paths, line numbers, and function names; use the project's domain language and include concrete reproduction steps so the issue stays valid after implementation changes.

When should a bug report be split into multiple issues?▼

Split when the fix spans independent areas, concerns can be worked on in parallel, or there are distinct failure modes. Keep it as one issue when a single behavior is wrong in one place or all symptoms share one root cause.

Does this QA skill require the GitHub CLI?▼

Yes, issues are created with gh issue create, so the GitHub CLI must be installed and authenticated against the target repository. Without it, the filing step cannot run.

Why should issues avoid file paths and line numbers?▼

File paths and line numbers go stale after refactors, making issues confusing or misleading. Describing observable behavior and reproduction steps keeps the issue accurate regardless of how the code is reorganized.

Related Skills

Explore More Software Engineering Skills→
jaredcroxtonjaredcroxton

github-auth

Configure GitHub authentication via HTTPS tokens, SSH keys, or gh CLI.

Community
Intermediate
nguyennd93nguyennd93

bug-triage

Prioritize and assign bugs by severity and priority, then generate a triage report.

Community
Advanced
forbotsakeforbotsake
5

qa

Run automated QA cycles with tiered testing and ship-readiness reporting.

Official
Advanced
hgxszhjhgxszhj

qa

Guide users to describe bugs and file GitHub issues with project language.

Community
Intermediate