Analyze QA reports against the codebase and draft technical issues.
npx skills add https://github.com/joshukraine/dotfiles --skill qa-triage
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
This Skill simplifies the process of triaging QA reports and drafting technical issues, saving time and reducing errors in the issue creation workflow.
Use the qa-triage skill to process a QA report and draft the corresponding technical issues.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
projectedanxManage GitHub issue lifecycles via CLI and REST API.
psd401Extract FreshService ticket details and create linked GitHub issues.
BrennonTWilliamsRefine software issue documentation via codebase research and gap analysis.
PelekeDraft structured GitHub issues with titles, descriptions, and acceptance criteria.
