qa-triage

Analyze QA reports against the codebase and draft technical issues.

421|49|Updated Jul 3, 2014

Search Tags:#code analysis #workflow automation #technical writing #issue creation #qa triage

Ready to run

npx skills add https://github.com/joshukraine/dotfiles --skill qa-triage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-triage
Source: https://github.com/joshukraine/dotfiles/tree/main/claude/.claude/skills/qa-triage
Command: npx skills add https://github.com/joshukraine/dotfiles --skill qa-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of triaging QA reports and drafting technical issues, saving time and reducing errors in the issue creation workflow.

Core Features & Use Cases

QA Report Triage: Analyze QA reports, classify them, and draft technical issues based on codebase investigation.
Codebase Confirmation: Confirm reported issues against the codebase, ensuring accurate problem identification.
Tech Issue Drafting: Create well-formed technical issues with acceptance criteria and closing plans.
Decision Gate: Stop for human approval before creating any issues, ensuring quality control.
Use Case: Use this Skill to process a QA report, analyze it against the code, and draft the corresponding technical issues for a software project.

Quick Start

Use the qa-triage skill to process a QA report and draft the corresponding technical issues.

Frequently Asked Questions about qa-triage

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

FAQPage Schema

How do I automate QA report triage and technical issue creation?▼

Automating QA report triage involves analyzing the report, classifying the issue type, and drafting a technical issue based on codebase investigation. This workflow requires GitHub API access and a project-specific CLAUDE.md file to apply local conventions.

What is the process for drafting technical issues from QA reports?▼

Drafting technical issues from QA reports involves confirming the reported problem against the codebase and creating well-formed issues with acceptance criteria and closing plans. A decision gate pauses the process for human approval before finalizing issue creation.

Can I use this workflow to classify QA issues against my existing codebase?▼

Yes, you can classify QA issues against your codebase by performing codebase analysis to ensure accurate problem identification. This confirms the reported issues exist before drafting the corresponding technical issues for your software project.

Do I need GitHub CLI access to automate software issue drafting?▼

Yes, you need GitHub CLI access to automate software issue drafting. The triage workflow relies on the GitHub API to perform codebase analysis, classify issue types, and create the technical issues within your project repository.

How do I ensure quality control when creating issues from QA reports?▼

To ensure quality control when creating issues from QA reports, the workflow implements a decision gate that stops for human approval before creating any issues. This prevents automated errors and ensures the drafted technical issues meet project standards.

What limitations exist when classifying QA reports into issue types?▼

A key limitation is the dependency on a project-specific CLAUDE.md file for local conventions and GitHub API access. Without these prerequisites, the codebase analysis and issue type classification cannot function accurately.