qa

Analyze code changes to plan targeted QA tests across personas for Contract Hub.

Updated Aug 27, 2026

Search Tags:#automation #testing #qa #web-testing #workflows #diff-analysis #agent-browser

Ready to run

npx skills add https://github.com/cptunderpantsmoons/contract-hubv1 --skill qa-cptunderpantsmoons

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/cptunderpantsmoons/contract-hubv1/tree/main/.factory/skills/qa
Command: npx skills add https://github.com/cptunderpantsmoons/contract-hubv1 --skill qa-cptunderpantsmoons

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams struggle to validate code changes across complex flows without repetitive manual testing; this skill orchestrates multi-persona QA coverage for Contract Hub.

Core Features & Use Cases

Diff-driven test planning: maps changes to targeted QA flows and personas.
Multi-persona QA: executes tests across qa_user and unauthenticated_user roles to validate security and access controls.
Evidence-backed reporting: collects evidence and generates consistent QA reports for PRs and releases.

Quick Start

Run the QA orchestrator against a PR or local build by loading .factory/skills/qa/config.yaml and executing the qa-web flows.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I automate end-to-end QA testing for code changes?▼

End-to-end QA automation analyzes code diffs to plan targeted web testing flows across multiple personas, executing agent-browser-based tests to validate changes and capture evidence for reporting.

What is diff-driven test planning and how does it work?▼

Diff-driven test planning maps code changes directly to targeted QA flows and user personas, ensuring only affected workflows are tested rather than running redundant full-suite manual checks.

How do I run multi-persona web testing to validate access controls?▼

Multi-persona web testing executes agent-browser flows across authenticated and unauthenticated user roles, validating security boundaries and access controls during PR or release validation.

Can I use agent-browser automation for smoke testing and release validation?▼

Agent-browser automation supports smoke testing and release validation by orchestrating configurable environment workflows, capturing evidence, and generating consistent QA reports for each scenario.

Do I need a configurable environment setup to run QA workflows?▼

Configurable environments are required to execute QA workflows, loaded via config.yaml files that define target builds, environments, and persona settings for agent-browser-based web testing orchestration.

What's the best way to generate evidence-backed QA reports for pull requests?▼

Evidence-backed QA reports are generated automatically by collecting artifacts during agent-browser test execution, mapping results to code diffs, and producing consistent validation documentation for PR review.