qa-site

Run mechanical checks and Claude-based reviews to produce QA reports and fix lists.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/calebaero/website-factory --skill qa-site
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-site
Source: https://github.com/calebaero/website-factory/tree/main/skills/qa-site
Command: npx skills add https://github.com/calebaero/website-factory --skill qa-site

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA-site automates the gate for deploying websites by running standardized mechanical checks and Claude-based reviews against qa-standards and security baselines. It generates both human-readable reports (qa-report.md) and machine-readable findings (qa-report.json), and a concrete fix list (fix-list.md) to unblock deployment. This reduces manual QA toil and guards against regressions in production-ready sites.

Core Features & Use Cases

  • Mechanical checks: re-run smoke checks, type checks, and builds when dependencies exist; collects outputs to surface failures early.
  • Claude-based review: analyzes the site structure, content, accessibility, SEO, and conversion readiness against qa-standards and security-baseline, producing qa-report.md and fix-list.md.
  • Outputs and workflow: writes qa-report.md, qa-report.json, and fix-list.md at the project root; updates marker status for deployment gating.

Quick Start

Invoke the QA gate on a built site by running /website-factory:qa-site <site-dir> after the site has been scaffolded and built.

Frequently Asked Questions about qa-site

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

FAQPage Schema
How do I automate end-to-end QA testing for a built website?

Automate end-to-end QA for built sites by running mechanical smoke checks and Claude-based reviews against content, SEO, and security baselines to generate structured reports and unblock deployment.

What is included in an automated website QA report?

An automated site QA report includes mechanical check outputs for types and builds, plus Claude-based reviews of accessibility, security, and SEO, producing qa-report.md, qa-report.json, and fix-list.md.

How do I generate a fix list for website deployment blockers?

Generate a deployment fix list by running an automated QA gate that analyzes site artifacts against qa-standards and security-baselines, outputting a concrete fix-list.md to guide remediation.

Can I run automated QA checks without modifying my source files or dependencies?

Yes, automated QA checks can run without modifying source files or dependencies by reading directly from the site's artifacts and plan data to evaluate compliance and guide remediation.

What's the best way to validate site accessibility and security before deployment?

Validate accessibility and security before deployment by running an automated QA gate that combines mechanical checks with Claude-based reviews against qa-standards and security-baseline to produce actionable reports.

When do I need to run an automated QA gate on a scaffolded site?

Run an automated QA gate on a scaffolded site after the build process is complete, ensuring the generated artifacts are validated against content-seo-standards and security-baseline before production deployment.