skills.rest
j172
j172COMMUNITY
Explore all skills by this author →
Website𝕏@j172GitHub

qa

Files durable GitHub issues from conversational QA bug reports.

Updated Jul 30, 2026
Search Tags:#testing#qa#bug report#github issues#gh cli#issue triage#codebase exploration
One-click install
npx skills add https://github.com/j172/bid --skill qa-j172
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/j172/bid/tree/main/agent/skills/qa
Command: npx skills add https://github.com/j172/bid --skill qa-j172

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reporting bugs is tedious: users must translate their experience into structured, well-scoped GitHub issues that developers can act on. This Skill runs an interactive QA session where the user describes problems conversationally, and the agent clarifies, explores the codebase for domain context, and files durable GitHub issues automatically. ## Core Features & Use Cases - Conversational bug intake: Users describe problems in their own words with at most 2-3 short clarifying questions about expected behavior, reproduction steps, and consistency. - Background codebase exploration: An Explore subagent learns the project's domain language and intended behavior so issues read naturally without citing files or line numbers. - Smart issue scoping: Decides whether a report is a single issue or should be broken into multiple thin, parallelizable issues with honest blocking relationships, filed in dependency order via gh issue create. - Use Case: During a QA pass on a web app, a user says "the form validation is wrong and the redirect after submit is broken." The agent splits this into two independently fixable GitHub issues with reproduction steps and shares the URLs. ## Quick Start Start a QA session and describe the bug you encountered so the agent can file a GitHub issue for it.

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 conversational bug report?▼

Describe the problem in your own words during the QA session. The agent asks at most 2-3 clarifying questions about expected behavior and reproduction steps, then files the issue with gh issue create and shares the URL.

How does the QA session decide to split one bug report into multiple issues?▼

It breaks a report down when the fix spans independent areas, has separable concerns different people could handle in parallel, or has distinct failure modes. Single-behavior problems stay as one issue.

Does the 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, issues cannot be filed.

Why do the filed issues avoid file paths and line numbers?▼

Issues are written to be durable so they still make sense after major refactors. They describe user-facing behaviors in the project's domain language rather than internal implementation details that go stale.

Can I review issues before they are filed?▼

No, the workflow files issues immediately without a review step and then shares the URLs. This keeps the session moving so you can report the next issue right away.

Related Skills

Explore More Software Engineering Skills→
intelligentcode-aiintelligentcode-ai
35

user-tester

Automate end-to-end user journey testing across web applications with Playwright or Puppeteer.

Official
Advanced
wildwasserwildwasser
35

issue-triage

Triage GitHub issues by reviewing, validating, labeling, and assigning owners.

Community
Intermediate
dnkrowdnkrow
1

smoke-check

Execute automated test suites and collect manual smoke-check confirmations for build readiness.

Community
Advanced
hgxszhjhgxszhj

qa

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

Community
Intermediate