qa

Tests web applications in a browser, fixes found bugs with atomic commits, and produces health-score reports.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill qa-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill qa-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually clicking through a web app to find bugs is slow and easy to skip before shipping. This Skill systematically QA-tests a web application like a real user, fixes the bugs it finds in source code with atomic commits, re-verifies each fix, and produces a before/after health score report. ## Core Features & Use Cases - Three testing tiers: Quick (critical/high severity only), Standard (+ medium), and Exhaustive (+ low/cosmetic), so you can match depth to your release timeline. - Diff-aware mode: On a feature branch with no URL given, it analyzes the branch diff, identifies affected pages and routes, and tests exactly what changed. - Test framework bootstrap: Detects your runtime (Node, Rails, Python, Go, Rust, PHP, Elixir), installs a test framework, writes real tests, sets up CI, and documents conventions in TESTING.md. - Regression mode: Compares a new run against a saved baseline.json to show which issues were fixed, which are new, and the health score delta. - Use Case: You just finished a feature branch and ask "does this work?" The Skill finds your local dev server, clicks through every affected page, documents a broken form submit with screenshots, fixes it in the source, commits the fix, and re-verifies. ## Quick Start Ask the assistant to run /qa on your current branch or a URL such as http://localhost:3000 to test the app and fix any bugs found.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I QA test my web app automatically before shipping?

Run the qa skill against a URL or your current feature branch. It navigates pages, clicks interactive elements, fills forms, checks console errors, documents issues with screenshots, then fixes bugs in source code with atomic commits and re-verifies each fix.

What is diff-aware QA testing on a feature branch?

Diff-aware mode analyzes your branch's git diff to identify affected pages, routes, and API endpoints, then tests only what changed. It auto-detects local dev servers on common ports like 3000, 4000, and 8080, so no URL is needed.

Can it set up a test framework if my project has none?

Yes. It detects your runtime (Node, Rails, Python, Go, Rust, PHP, Elixir), researches current best practices, installs a framework like vitest or pytest, writes 3-5 real tests, adds a GitHub Actions CI workflow, and documents conventions in TESTING.md.

Does the QA skill work with authenticated pages and 2FA?

Yes. It supports credential-based login, cookie file import, and CDP mode that reuses your real browser's existing sessions. For 2FA or CAPTCHA, it pauses and asks you to complete the step before continuing.

Why does the QA skill require a clean git working tree?

Each bug fix gets its own atomic commit, so uncommitted changes would mix with fix commits. If the tree is dirty, it stops and offers to commit or stash your changes before starting.

How is the QA health score calculated?

The score is a weighted average across eight categories: console errors, links, visual, functional, UX, performance, content, and accessibility. Each category starts at 100 and deducts points per issue by severity, from -25 for critical to -3 for low.