skills.rest
AgentiveStack
AgentiveStackOFFICIAL
Explore all skills by this author →
WebsiteGitHub

qa

Guide conversational QA sessions to file durable GitHub issues.

71|17|Updated Apr 24, 2026
Search Tags:#qa#github issues#codebase exploration#bug reporting#domain language
One-click install
npx skills add https://github.com/AgentiveStack/skills --skill qa-agentivestack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/AgentiveStack/skills/tree/main/qa
Command: npx skills add https://github.com/AgentiveStack/skills --skill qa-agentivestack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables a conversational QA workflow that helps you describe bugs in plain language while the agent explores the codebase for context and files durable GitHub issues using the project's domain language.

Core Features & Use Cases

  • Interactive bug description and clarifying questions to narrow scope
  • Background codebase exploration to surface domain terms and invariants
  • Durable, domain-language issue creation that aligns with project terminology
  • Context-aware QA testing and issue triage to accelerate discovery and repair

Quick Start

Describe a bug in natural language to start the QA session.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I create durable GitHub issues from bug reports?▼

To create durable GitHub issues from bug reports, describe the bug in natural language to start a conversational QA session that explores the codebase for context and files the issue using project domain language.

What is domain language alignment in bug reporting?▼

Domain language alignment in bug reporting means structuring issue descriptions using the project's specific terminology and invariants, which is achieved by exploring the codebase to surface accurate domain terms during the QA session.

Can I report bugs without exposing internal file paths or implementation details?▼

Yes, you can report bugs without exposing internal file paths because the workflow focuses on context exploration and domain language alignment, ensuring durable issue creation omits implementation details from the final GitHub issue.

How do I streamline QA testing and bug discovery across projects?▼

You can streamline QA testing and bug discovery across projects by engaging in an interactive session where clarifying questions narrow the bug scope and background codebase exploration surfaces relevant domain terms for context-aware issue triage.

Do I need to manually format bug descriptions before filing GitHub issues?▼

No, you do not need to manually format bug descriptions before filing GitHub issues because the conversational agent guides the interactive bug description process and automatically structures the final issue using project terminology.

What is the best way to triage bugs using project terminology?▼

The best way to triage bugs using project terminology is to use a context-aware QA session that applies domain language alignment, ensuring the filed GitHub issues match the project's established invariants and domain language.

Related Skills

Explore More Software Engineering Skills→
hgxszhjhgxszhj

zoom-out

Generate a project-wide module and caller topology map from codebase structure.

Community
Intermediate
kinncjkinncj
23

gh-projects

Automates GitHub Project V2 board management by adding issues and updating fields.

Community
Intermediate
prof-danielcprof-danielc

speckit.checker

Run static analysis tools and aggregate results into a prioritized issue report.

Community
Advanced
bradtaylorsfbradtaylorsf
8

linear-ticket-analysis

Analyze Linear tickets to detect duplicates and investigate Git history for fixes.

Community
Intermediate