How do I install the QA skill?

Run npx skillmds@latest add floomhq/qa in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with QA?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

floomhq (@floomhq) published this skill. Their other Agent Skills are listed on their SkillMD profile.

QA by floomhq — Agent Skill

Name: QA
Author: floomhq

Analyze a diff or set of changes and identify which pages, routes, components, and systems are affected. Use before shipping code, when asked to "qa this", "review my changes", "what's affected", "blast radius", or "qa check". Produces a structured impact analysis.

floomhq d57994e 2.1 KB Updated Sep 17, 2026

File contents

QA Skill

Step 1: Get the diff

git diff main...HEAD
# or for staged changes:
git diff --cached
# or for a specific commit range:
git diff <from>..<to>

Step 2: Categorize changes

For each changed file, identify:

Type: frontend / backend / config / tests / docs / infra
Scope: which feature/module/route is affected
Risk: low / medium / high

Step 3: Impact analysis

Frontend changes

Which pages/routes render the changed components?
Are there loading/error states to test?
Are there mobile/desktop variants to check?
Does the change affect layout shift or performance?

Backend changes

Which API endpoints are affected?
Which consumers call those endpoints?
Are there database queries that changed?
Are there cron jobs or background tasks affected?

Config/env changes

Which environments are affected?
Is there a migration or deployment step needed?
Are there secrets that need to be rotated or updated?

Breaking changes

Are any public interfaces changing signature?
Are any database schemas changing?
Are any API contracts changing?

Step 4: Test plan

Generate a concrete test checklist based on the affected areas:

TEST PLAN for this diff:

Pages/routes to verify:
- [ ] /path/to/page - verify [specific behavior]
- [ ] /other/route - verify [specific behavior]

API endpoints to verify:
- [ ] GET /api/endpoint - verify [expected response]

Edge cases to check:
- [ ] [specific edge case]
- [ ] [error state]

Regression checks (ensure nothing broke):
- [ ] [existing feature that could be affected]

Step 5: Risk summary

QA SUMMARY
Files changed: N
Risk level: [LOW / MEDIUM / HIGH]
Affected areas: [list]
Manual testing required: [YES / NO]
Recommended: [SHIP / NEEDS MORE TESTING / STOP]

---name: qadescription: Analyze a diff or set of changes and identify which pages, routes, components, and systems are affected. Use before shipping code, when asked to "qa this", "review my changes", "what's affected", "blast radius", or "qa check". Produces a structured impact analysis.---# QA Skill## Step 1: Get the diff```bashgit diff main...HEAD# or for staged changes:git diff --cached# or for a specific commit range:git diff <from>..<to>```## Step 2: Categorize changesFor each changed file, identify:- **Type**: frontend / backend / config / tests / docs / infra- **Scope**: which feature/module/route is affected- **Risk**: low / medium / high## Step 3: Impact analysis### Frontend changes- Which pages/routes render the changed components?- Are there loading/error states to test?- Are there mobile/desktop variants to check?- Does the change affect layout shift or performance?### Backend changes- Which API endpoints are affected?- Which consumers call those endpoints?- Are there database queries that changed?- Are there cron jobs or background tasks affected?### Config/env changes- Which environments are affected?- Is there a migration or deployment step needed?- Are there secrets that need to be rotated or updated?### Breaking changes- Are any public interfaces changing signature?- Are any database schemas changing?- Are any API contracts changing?## Step 4: Test planGenerate a concrete test checklist based on the affected areas:```TEST PLAN for this diff:Pages/routes to verify:- [ ] /path/to/page - verify [specific behavior]- [ ] /other/route - verify [specific behavior]API endpoints to verify:- [ ] GET /api/endpoint - verify [expected response]Edge cases to check:- [ ] [specific edge case]- [ ] [error state]Regression checks (ensure nothing broke):- [ ] [existing feature that could be affected]```## Step 5: Risk summary```QA SUMMARYFiles changed: NRisk level: [LOW / MEDIUM / HIGH]Affected areas: [list]Manual testing required: [YES / NO]Recommended: [SHIP / NEEDS MORE TESTING / STOP]```

Frequently asked questions

QA