borghei/qa-browser-automation
> Browser-based QA combining Chrome MCP control with Python analysis tools. Use when performing browser QA testing, visual regression tracking, WCAG accessibility auditing, performance profiling, or health-scoring web applications.
npx skills add https://github.com/borghei/Claude-Skills --skill qa-browser-automation
The agent drives Chrome MCP for live browser testing and uses four Python tools for deterministic health scoring, accessibility auditing, visual regression tracking, and report generation.
Before the QA sweep, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
# Score QA findings (0-100 weighted across 10 categories)
python scripts/qa_health_scorer.py findings.json --threshold 85 --baseline .qa-baselines/latest.json --save-baseline --json
# Audit HTML for WCAG 2.1 violations
python scripts/accessibility_auditor.py page.html --level AA --json
# Track visual regressions
python scripts/visual_regression_tracker.py --init --baseline-dir ./baselines
python scripts/visual_regression_tracker.py --register ./baselines
python scripts/visual_regression_tracker.py --baseline ./baselines --current ./screenshots --threshold 5
# Generate full QA report
python scripts/test_report_generator.py session_data.json --format markdown -o report.md
| Tool | Input | Output |
|------|-------|--------|
| qa_health_scorer.py | Findings JSON | Score 0-100, grade A-F, category breakdown, trend data |
| accessibility_auditor.py | HTML file (or stdin) | WCAG violations by level with remediation guidance |
| visual_regression_tracker.py | Baseline + current screenshot dirs | Pass/fail per page, change percentages |
| test_report_generator.py | Session data JSON | Markdown or JSON report with recommendations |
All tools support --json for machine output. Health scorer and regression tracker return exit code 1 on failure (CI-friendly).
Phase 1-2: Pre-flight and authentication.
git status is clean. Abort if dirty..qa-sessions/{timestamp}/Phase 3-4: Orient and explore.
mcp__claude-in-chrome__read_page to build sitemap/page map.read_console_messages for errors, read_network_requests for 4xx/5xx.Phase 5: State testing.
Phase 6: Cross-device and security.
Phase 7-8: Document and score.
python scripts/qa_health_scorer.py findings.json --baseline .qa-baselines/latest.jsonPhase 9: Triage and fix loop.
git revert.Phase 10-11: Regression check and report.
python scripts/test_report_generator.py session.json --save-baselineValidation checkpoint: Health score >= 85. Zero P0 findings. WCAG AA >= 95%.
# Set up baseline
python scripts/visual_regression_tracker.py --init --baseline-dir ./baselines
# Capture and register screenshots
python scripts/visual_regression_tracker.py --register ./baselines
# After changes, compare
python scripts/visual_regression_tracker.py --baseline ./baselines --current ./screenshots --threshold 5 --json
# Accept intentional changes
python scripts/visual_regression_tracker.py --update-baseline --baseline ./baselines --current ./screenshots
Pages exceeding the threshold (default 5%) are flagged as regressions. Uses SHA-256 hashing and byte-level comparison.
python scripts/accessibility_auditor.py page.html --level AA --json
curl -s https://example.com | python scripts/accessibility_auditor.py - --level AAA
What gets checked by level:
Each violation includes: WCAG criterion, severity, element selector, and remediation guidance.
| Tier | Duration | Scope |
|------|----------|-------|
| Quick | 30s | Console errors, broken links, basic a11y, mobile resize |
| Standard | 2-5 min | + Top 10 routes, forms, contrast, Core Web Vitals |
| Deep | 10-20 min | + Full sitemap, state testing, WCAG AA, performance, visual regression, security headers |
| Exhaustive | 30+ min | + Every element, WCAG AAA, all pages performance, 5 breakpoints, auth edge cases, memory leaks |
10 weighted categories, score 0-100:
| Category | Weight | Measures |
|----------|--------|----------|
| Functional | 18% | Forms, CRUD, navigation flows |
| Accessibility | 13% | WCAG compliance, keyboard nav |
| Console Errors | 12% | JS errors, unhandled rejections |
| UX Flow | 12% | Logical navigation, clear feedback |
| Performance | 12% | Core Web Vitals within thresholds |
| Visual Consistency | 10% | Layout shifts, alignment, z-index |
| Broken Links | 8% | HTTP 4xx/5xx, dead anchors |
| Content Quality | 5% | Spelling, placeholder text, truncation |
| Security Headers | 5% | CSP, HSTS, cookie flags |
| Mobile Responsive | 5% | Breakpoints, touch targets, no h-scroll |
Severity deductions: P0: -30, P1: -18, P2: -10, P3: -4, P4: -1.
Grades: A (90-100), B (80-89), C (70-79), D (60-69), F (0-59).
git status dirty.fix(qa): [P{severity}] {description}| Problem | Cause | Solution |
|---------|-------|----------|
| Scorer exits code 1 with no errors | Score below --threshold (default 70) | Check score in output; raise threshold or fix findings |
| Auditor reports parse-error | Malformed HTML | Verify file is complete; check curl is not returning redirect |
| Regression tracker 100% change on all pages | Baseline manifest empty | Run --init then --register before comparing |
| Findings default to P3/functional | Missing severity or category keys | Include both keys in each finding dict |
| Chrome MCP returns stale content after SPA nav | DOM updated without full page load | Wait for transition, call read_page again |
| Guide | Path |
|-------|------|
| Browser Testing Methodology | references/browser_testing_methodology.md |
| WCAG Compliance Guide | references/wcag_compliance_guide.md |
| Performance Benchmarks | references/performance_benchmarks.md |
| Skill | Integration |
|-------|-------------|
| code-reviewer | Health score and findings in PR review context |
| senior-frontend | Visual regression baselines align with component library |
| senior-devops | Health score gates CI/CD via exit code |
| senior-secops | Security header findings escalate to security review |
| incident-commander | P0 findings trigger incident response |
Last Updated: April 2026
Version: 2.1.0
Take borghei/qa-browser-automation from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.