qa-testing
Run QA testing on a page, feature, or full site at one of three depth tiers (smoke, standard, full). Use this skill whenever the user asks to test a page, audit a site, check for bugs, verify a deploy, run a QA sweep, or review accessibility, performance, or SEO basics. Triggers on test, QA, audit, verify, check, is it working, does it look right, broken, 404, image not loading, post-deploy check, regression test. Also triggers proactively after any significant code change or new page launch where verification matters.
Profile →npx skills add rampstackco/claude-skills --skill qa-testing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# QA Testing Verify that a page, feature, or site is working before declaring it shipped. Stack-agnostic. Console-snippet driven for speed. This skill is faster than `accessibility-audit` (which goes deeper on WCAG) and `performance-optimization` (which goes deeper on Core Web Vitals). Use this skill for general QA. Use the specialists for deep audits. --- ## When to use - After every deploy (smoke test) - After launching a new page or feature (standard audit) - Before a major release (full release matrix) - Investigating a "something looks off" report - Pre-launch verification of a site or section ## When NOT to use - Deep accessibility compliance work (use `accessibility-audit`) - Deep performance investigation (use `performance-optimization`) - Code review or debugging (use `code-review-web`) - Initial site setup or technical SEO baseline (use `seo-technical`) --- ## Required inputs - The page URL or site under test - The tier of QA needed (smoke, standard, or full) - Browser dev tools access - Any specific concerns to check beyond the standard tier --- ## The framework: 3 tiers QA scales with the stakes. Pick the tier that matches the context. | Tier | When to run | Time | Cove
- When to use
- When NOT to use
- Required inputs
- The framework: 3 tiers
- Tier 1: Smoke test
- Tier 2: Standard page audit
- Tier 3: Full release matrix
- Specific QA snippets
- Image audit
- Heading hierarchy check
- Contrast spot-check
- Form audit (per form)
- External link audit
- Workflow
What does the qa-testing skill do?
Run QA testing on a page, feature, or full site at one of three depth tiers (smoke, standard, full). Use this skill whenever the user asks to test a page, audit a site, check for bugs, verify a deploy, run a QA sweep, or review accessibility, performance, or SEO basics. Triggers on test, QA, audit, verify, check, is it working, does it look right, broken, 404, image not loading, post-deploy check, regression test. Also triggers proactively after any significant code change or new page launch where verification matters.
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill qa-testing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.