skills.rest
maxenergy
maxenergyCOMMUNITY
Explore all skills by this author →
Website𝕏@maxenergyluoGitHub

qa

Coordinates interactive QA sessions and files GitHub issues from user-described bugs with domain language and templates.

Updated May 2, 2026
Search Tags:#codebase#qa#reproducibility#github-issues#bug-report#issue-template#domain-language
One-click install
npx skills add https://github.com/maxenergy/skills --skill qa-maxenergy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/maxenergy/skills/tree/main/skills/deprecated/qa
Command: npx skills add https://github.com/maxenergy/skills --skill qa-maxenergy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interactive QA sessions help users articulate bugs clearly and automatically generate GitHub issues, reducing back-and-forth and miscommunication.

Core Features & Use Cases

  • Interactive QA session that captures user-described bugs in plain language.
  • Background codebase exploration to learn domain language and gather context.
  • Durable GitHub issue creation with templates, supporting single or multi-issue breakdown.
  • Guidance to ensure clear reproduction steps and user-focused language, even after code changes.

Quick Start

Ask the agent to begin a QA session and describe the bug you want reported so it will file a durable GitHub issue.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automatically create GitHub issues from user-reported bugs?▼

You can file GitHub issues from user-reported bugs by running an interactive QA session that listens to plain language descriptions, asks limited clarifying questions, and generates structured issues with domain-language phrasing and reproducible steps.

What is the best way to ensure bug reports stay clear after code refactors?▼

Bug reports stay clear after code refactors by using non-code and domain-language phrasing rather than referencing specific implementation details. This approach ensures the issue context remains valid and understandable even when the underlying codebase changes.

Can I break down a complex bug report into multiple sub-issues on GitHub?▼

Yes, you can break down complex bug reports into multiple sub-issues. The QA session explores the codebase in the background for context and supports generating multiple durable GitHub issues from a single interactive bug reporting session.

Do I need to provide codebase access for an interactive QA session?▼

Codebase access is needed for the QA session to explore the codebase in the background, gather context, and learn the domain language. This allows the generated GitHub issues to accurately reflect the project's terminology and structure.

How do I guide users to provide reproducible steps in a bug report?▼

Guide users to provide reproducible steps by running an interactive QA session that asks limited clarifying questions. This enforces structured templates and user-focused language to ensure the final GitHub issue contains clear reproduction steps.

Why use domain language instead of code references when filing GitHub issues?▼

Use domain language instead of code references because it ensures the GitHub issues remain clear and accurate over time. This non-code guidance prevents issues from becoming obsolete when the codebase undergoes refactoring.

Related Skills

Explore More Software Engineering Skills→
ruskibeatsruskibeats

qa

Create GitHub issues from conversational bug reports with codebase context.

Community
Intermediate
joeczarjoeczar

milestone-tracker

Fetch GitHub milestones and issues to compute completion percentages.

Community
Intermediate
amdmaxamdmax
2

bug-fix

Automate bug investigation, fixing, and regression testing from a GitHub backlog.

Community
Advanced
yashs33244yashs33244
1

qa

Convert bug conversations into GitHub issues with reproduction steps.

Community
Intermediate