rc-qa-execution

Executes full-project QA by running build, test, CLI, API, and browser flows against a repository.

19|1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/rodolfochicone/rc-project --skill rc-qa-execution-rodolfochicone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rc-qa-execution
Source: https://github.com/rodolfochicone/rc-project/tree/main/skills/misc/rc-qa-execution
Command: npx skills add https://github.com/rodolfochicone/rc-project --skill rc-qa-execution-rodolfochicone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Validating a branch or release candidate requires more than running unit tests: you must discover the repository's own verification commands, exercise real user flows through CLI, HTTP, and browser interfaces, fix regressions at the root cause, and produce evidence-backed reports. This Skill automates that entire QA execution loop. ## Core Features & Use Cases - Contract Discovery: Runs a discovery script that scans Makefiles, package.json, go.mod, Cargo.toml, pyproject.toml, and CI workflows to surface the canonical install, lint, test, build, and start commands, plus Web UI and E2E harness signals. - End-to-End Flow Execution: Drives CLI and API workflows through public interfaces and exercises critical browser flows via the agent-browser CLI with screenshot evidence at every checkpoint. - Regression Diagnosis and Reporting: Reproduces failures, fixes root causes, adds E2E coverage where supported, and files structured BUG issues plus a verification report with pass/fail verdicts. - Use Case: Before merging a risky commit, invoke this Skill to run the full verification gate, test three critical browser flows, fix a discovered regression, and produce a verification report with screenshots and issue files. ## Quick Start Run full QA on this repository and store all issues, screenshots, and the verification report under ./qa-output.

Frequently Asked Questions about rc-qa-execution

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

FAQPage Schema
How do I run full-project QA on a repository before release?▼

Invoke the skill with an optional output path. It discovers the repository's verify, build, test, and start commands, runs the baseline gate, exercises CLI, API, and browser flows, fixes regressions, and writes a verification report with evidence.

How does the skill detect a project's test and build commands?▼

It runs scripts/discover-project-contract.py, which parses Makefiles, Justfiles, package.json, go.mod, Cargo.toml, pyproject.toml, and GitHub Actions workflows to surface candidate install, lint, test, build, and start commands per ecosystem.

Does it support browser-based end-to-end testing?▼

Yes, when a Web UI surface is detected it uses the agent-browser CLI to run open, snapshot, interact, re-snapshot, verify loops across 3-5 critical flows, capturing screenshots and testing forms, navigation, errors, and viewports.

What happens if the repository has no E2E test harness?▼

The skill does not bootstrap a new framework during QA. It keeps live manual evidence, classifies flows as manual-only or blocked, and documents the automation gap in the verification report.

What artifacts does the QA run produce?▼

It writes BUG-<num>.md issue files with severity and priority, screenshots per browser flow, and a verification report containing commands, exit codes, verdicts, automated coverage status, and browser evidence under the QA output directory.