skills.rest
alexandrbasis
alexandrbasisCOMMUNITY
Explore all skills by this author →
Website𝕏@alexandrbasisGitHub

qa

Facilitate interactive QA sessions to file bugs as Linear or GitHub issues.

12|2|Updated Nov 20, 2025
Search Tags:#automation#codebase#qa#issue-management#bug-tracking#domain-language
One-click install
npx skills add https://github.com/alexandrbasis/claudops --skill qa-alexandrbasis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/alexandrbasis/claudops/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/alexandrbasis/claudops --skill qa-alexandrbasis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This QA workflow helps users report bugs in a conversational session and converts them into durable tracker issues (GitHub or Linear) with domain-language terminology, enabling structured triage and ongoing backlog management.

Core Features & Use Cases

  • Interactive QA session that elicits bug reports from the user in natural language.
  • Automatically files issues as Linear or GitHub issues using the session's context and domain language.
  • Explores the codebase in the background to gather context and ensure accurate issue framing.
  • NOT for single-bug triage or interactive debugging; works best for multi-issue QA passes.

Quick Start

Engage in a guided QA session by describing the problems you want to track and let the agent create durable issues in your chosen tracker.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I file bug tracker issues from an interactive QA session?▼

You can file bug tracker issues by engaging in an interactive QA session where you describe problems in natural language, and the agent automatically files durable issues in Linear or GitHub using domain-language terminology.

Can I run a multi-issue QA pass across a codebase and automatically create Linear tickets?▼

Yes, you can run multi-issue QA passes across codebases where the agent explores context in the background and files durable issues directly in Linear or GitHub as you describe each problem.

Do I need a configured issue tracker to run conversational bug tracking?▼

Yes, you need a configured issue tracker like Linear or GitHub to file durable issues, and proper SKILL.md frontmatter with name and description must be set up for the agent to function correctly.

What is the best way to report multiple bugs found during codebase QA?▼

The best way to report multiple bugs is through a guided QA session where you describe the problems conversationally, allowing the agent to explore the codebase and craft accurately framed issues for your backlog.

Why does this QA workflow not perform code changes or interactive debugging?▼

This QA workflow does not perform code changes or interactive debugging because it is specifically designed for multi-issue QA passes to surface bugs and file structured tracker issues, not for single-bug triage.

When should I not use this approach for issue management?▼

You should not use this approach for single-bug triage or interactive debugging, as it is optimized for multi-issue QA passes across codebases where users describe problems for the agent to file as durable tracker issues.

Related Skills

Explore More Software Engineering Skills→
InditexTechInditexTech
195

qa

Convert conversational bug reports into durable GitHub issues.

Official
Intermediate
ReefBytesReefBytes
1

issue-triage

Automate Linear backlog triage to detect duplicates, stale issues, and priority misalignments.

Community
Advanced
kvithayathilkvithayathil

qa

Convert conversational bug reports into structured GitHub issues with codebase context.

Community
Intermediate
yash-gargyash-garg

qa

Convert conversational bug reports into structured GitHub issues.

Community
Advanced