skills.rest
malinskibeniamin
malinskibeniaminCOMMUNITY
Explore all skills by this author →
GitHub

qa

Document and triage bugs through structured QA sessions with GitHub issue creation.

3|1|Updated Mar 23, 2026
Search Tags:#workflow#qa#issue-tracking#conversational-ai#code-exploration#bug-triage
One-click install
npx skills add https://github.com/malinskibeniamin/skills --skill qa-malinskibeniamin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/malinskibeniamin/skills/tree/main/qa
Command: npx skills add https://github.com/malinskibeniamin/skills --skill qa-malinskibeniamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This QA process guides teams through structured, conversational bug/feature intake and issue filing, ensuring clear problem statements and contextual exploration before creating issues.

Core Features & Use Cases

  • Structured questioning to elicit expected vs actual behavior, repro steps, and context.
  • Codebase exploration to build domain understanding (check CONTEXT.md if present) and capture relevant domain language.
  • Issue scoping to decide between a single issue or breaking down into multiple issues with clear dependencies.
  • GitHub issue creation guidance to generate well-formed, contextual issues and references.
  • Optional browser state capture to observe user-facing behavior when needed.

Quick Start

Start a QA session by describing the issue; the agent will ask concise clarifying questions and explore the codebase for context.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I streamline bug triage and issue intake through conversational AI?▼

Streamline bug triage by guiding teams through structured QA sessions that elicit expected versus actual behavior, explore the codebase for context, and generate well-formed GitHub issues.

What is the best way to document feature requests and scope them into multiple issues?▼

Document feature requests through conversational intake, then scope them by deciding between a single issue or breaking them down into multiple issues with clear dependencies before filing.

How do I gather codebase context while triaging bugs to ensure clear problem statements?▼

Gather codebase context during bug triage by exploring the repository, checking for a CONTEXT.md file to build domain understanding, and capturing relevant domain language for the issue.

Can I capture browser state during a QA session to observe user-facing behavior?▼

Yes, you can optionally capture browser state during a QA session to observe user-facing behavior, which helps document accurate reproduction steps for the bug being triaged.

Does this conversational issue tracking workflow require any specific dependencies?▼

No, this conversational issue tracking workflow requires no specific dependencies, allowing teams to start a QA session immediately by describing the issue for the agent to clarify and explore.

Why should I use a structured QA protocol for filing GitHub issues instead of manual entry?▼

Use a structured QA protocol for filing GitHub issues because it enforces steps like listening, clarifying, and exploring, ensuring clear problem statements and contextual references before creation.

Related Skills

Explore More Software Engineering Skills→
MissTullyMissTully

context-save

Capture git state, decisions, and remaining tasks into a portable snapshot.

Community
Advanced
probationer070probationer070

triage

Automate GitHub issue triage with a structured state machine.

Community
Intermediate
kartikkabadikartikkabadi

qa

Converts conversational bug reports into GitHub issues with reproduction steps.

Community
Advanced
OzeroHAXOzeroHAX
32

docs-report-bug-reporting

Generate structured bug reports with reproduction steps and impact assessment.

Community
Basic