菜单
Diff-aware QA routing — analyze what changed and route to the right test strategy. USE WHEN qa, what should I test, check my changes, run qa, review changes, diff analysis, what broke, smoke test, test routing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see AnalyticsTracking. USE WHEN ab test, split test, experiment setup, A/B test, multivariate.
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see AbTestSetup. USE WHEN analytics, tracking, GA4, measurement, Google Analytics.
Structure raw ideas into articulate outlines using Dan Koe's frameworks. USE WHEN articulate, structure ideas, outline talk, outline article, think through piece, brainstorm structure, how should I say this, organize my thoughts, structure this post, help me outline.
Balaji Srinivasan slide design system. USE WHEN balaji slides, balaji style, evidence slides, balaji presentation, split layout slides, create balaji deck, artifact-driven slides.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' USE WHEN competitor, alternatives page, vs page, comparison.
When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' USE WHEN edit copy, proofread, copy review, grammar check.
| name | QA |
| description | Diff-aware QA routing — analyze what changed and route to the right test strategy. USE WHEN qa, what should I test, check my changes, run qa, review changes, diff analysis, what broke, smoke test, test routing. |
Diff-aware quality assurance. Analyzes git diffs, classifies file changes by category (style, component, API, data, config, test, docs, infra), and routes to the appropriate test/validation strategy. Smart QA — test what matters, skip what doesn't.
Before executing, check for user customizations at:
~/.claude/skills/PAI/USER/SKILLCUSTOMIZATIONS/QA/
If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.
When executing a workflow, do BOTH:
Send voice notification:
curl -s -X POST http://localhost:8888/notify \
-H "Content-Type: application/json" \
-d '{"message": "Running the WORKFLOWNAME workflow in the QA skill to ACTION"}' \
> /dev/null 2>&1 &
Output text notification:
Running the **WorkflowName** workflow in the **QA** skill to ACTION...
| Workflow | Trigger | File |
|---|---|---|
| Analyze | "/qa", "what should I test", "check my changes", "diff analysis" | Workflows/Analyze.md |
| QuickCheck | "quick check", "smoke test", "quick qa", "sanity check" | Workflows/QuickCheck.md |
Two-stage process:
Tools/DiffAnalyzer.ts) — deterministic diff parsing, file classification, route generationPath: ~/.claude/skills/QA/Tools/DiffAnalyzer.ts
Usage:
# Diff against main (default)
bun ~/.claude/skills/QA/Tools/DiffAnalyzer.ts
# Diff against specific branch
bun ~/.claude/skills/QA/Tools/DiffAnalyzer.ts --branch develop
# Staged changes only
bun ~/.claude/skills/QA/Tools/DiffAnalyzer.ts --staged
# Explicit file list
bun ~/.claude/skills/QA/Tools/DiffAnalyzer.ts --files "src/api.ts,src/styles.css"
Output: JSON with file classifications, diff stats, and QA routing recommendations.
| Category | Matches | QA Strategy |
|---|---|---|
| style | CSS, SCSS, Tailwind config | Visual regression — screenshot before/after |
| component | TSX, JSX, Vue, Svelte | Component render check — verify UI |
| api | Route handlers, controllers, middleware | Endpoint validation — test request/response |
| data | Migrations, schemas, seeds, Prisma | Migration safety — check destructive ops |
| config | JSON, YAML, TOML, env files | Config validation — syntax and required fields |
| test | .test., .spec., tests | Test-only — run modified tests |
| docs | Markdown, README, CHANGELOG | Documentation review — link and accuracy check |
| infra | Dockerfile, CI/CD, deploy configs | Infrastructure review — verify deploy config |
| Size | Lines Changed | Strategy |
|---|---|---|
| Small | <50 | Quick smoke test — focused verification |
| Medium | 50-199 | Standard testing — run related tests |
| Large | 200+ | Full suite — comprehensive check recommended |
Example 1: Before shipping a feature
User: "/qa"
→ Runs DiffAnalyzer.ts against main
→ "12 files changed: 3 component, 2 api, 1 style, 6 test"
→ Routes: visual check for style, endpoint validation for API, run component tests
→ Executes each route, reports results
Example 2: Quick sanity check
User: "quick check"
→ Runs DiffAnalyzer.ts --staged
→ "2 files changed: 1 config, 1 api (small diff)"
→ Quick smoke test: validate config syntax, curl API endpoint
Example 3: Explicit files
User: "qa these files: src/auth.ts, src/auth.test.ts"
→ Runs DiffAnalyzer.ts --files "src/auth.ts,src/auth.test.ts"
→ Routes: API validation for auth.ts, run auth.test.ts
/qa before /ship to verify changes