QA

Analyze git diffs to route code changes to QA testing strategies.

2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/phuaky/pai-skills --skill qa-phuaky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: QA
Source: https://github.com/phuaky/pai-skills/tree/main/skills/QA
Command: npx skills add https://github.com/phuaky/pai-skills --skill qa-phuaky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff-aware QA routing guides testing effort by analyzing git diffs, classifying changes by category (style, component, API, data, config, test, docs, infra), and routing to the appropriate validation strategy.

Core Features & Use Cases

  • Diff-aware analysis of code changes and automatic routing to the correct QA workflow.
  • Customization via USER SKILLCUSTOMIZATIONS to override defaults and preferences.
  • Two-stage architecture: a deterministic DiffAnalyzer tool and AI orchestration to execute routing decisions and report results.
  • Structured JSON output of routing recommendations for integration with downstream tooling and evals.

Quick Start

Run the DiffAnalyzer to analyze your changes and generate QA routing recommendations by executing bun ~/.claude/skills/QA/Tools/DiffAnalyzer.ts with the appropriate flags.

Frequently Asked Questions about QA

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

FAQPage Schema
How do I analyze git diffs to determine the correct QA testing strategy?

You can analyze git diffs for QA routing by executing the DiffAnalyzer tool with bun against your repository changes. It classifies files into categories like style, component, API, and infra to generate structured JSON routing recommendations.

What is diff-aware QA routing and how does it work?

Diff-aware QA routing analyzes git diffs to classify changes across categories like style, component, API, data, config, test, docs, and infra. It then maps each category to targeted validation strategies to guide testing effort where it matters.

Can I customize QA routing rules for different code change categories?

Yes, you can override default QA routing behavior by injecting USER SKILLCUSTOMIZATIONS. This lets you tailor validation workflows and routing preferences for specific file categories like API, data, config, or infra changes.

How do I get structured JSON output for QA testing recommendations?

You can get structured JSON output for QA testing recommendations by running the DiffAnalyzer on your git diffs. The tool outputs per-file-category routing decisions in JSON format, enabling seamless integration with downstream tooling and evals.

Does git diff analysis work for routing infrastructure and config changes?

Yes, git diff analysis supports routing infrastructure and config changes by classifying them into dedicated infra and config categories. The routing workflow then maps these file types to their appropriate validation strategies.