pmos-testing-acceptance

Run automated lint, typecheck, test, and build gates before user review.

Updated May 9, 2026

Search Tags:#acceptance testing #release readiness #ci gating #frontend regression #crud validation #browser checks

Ready to run

npx skills add https://github.com/RhyTsui/PMOS --skill pmos-testing-acceptance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pmos-testing-acceptance
Source: https://github.com/RhyTsui/PMOS/tree/main/skills/pmos-testing-acceptance
Command: npx skills add https://github.com/RhyTsui/PMOS --skill pmos-testing-acceptance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PMOS work can look complete in a demo but fail in real delivery, so teams need strict, automated acceptance verification before user review and release.

Core Features & Use Cases

Automated acceptance gating: Turns lint, typecheck, tests, and browser regression into a fail-closed release readiness lane.
Frontend anti-demo validation: Verifies UI is not a landing/demo page, respects contracts, and confirms critical CRUD flows with error/loading/empty states.
Traceable outcomes and blockers: Produces clear tested/passed/failed results and explicitly blocks user review when checks fail.

Quick Start

Run the skill to verify a release candidate by executing static checks first, then tests, then relevant browser/workflow regression, and return a decision on whether user review must be blocked.

Frequently Asked Questions about pmos-testing-acceptance

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

FAQPage Schema

How do I gate releases with automated acceptance testing before user review?▼

Release gating uses a fail-closed chain of lint, typecheck, test, and build checks, followed by browser and workflow regression, to produce an explicit unblock or block decision for user review.

What is CI-grade release readiness verification for product delivery?▼

CI-grade release readiness is a strict automated verification process that ensures product changes pass static checks, CRUD regression, and browser regression before reaching user review.

How do I validate frontend UI is not a demo page during acceptance testing?▼

Frontend anti-demo validation verifies the UI respects contracts and confirms critical CRUD flows, including error, loading, and empty states, preventing incomplete interfaces from passing acceptance.

Can I block user review automatically when regression checks fail?▼

Yes, the fail-closed chain explicitly blocks user review when checks fail, providing clear tested artifacts and pass or fail outcomes to ensure only verified changes proceed.

What is the best way to automate CRUD regression and browser checks for release readiness?▼

Automate CRUD regression and browser checks by running static checks first, then tests, then relevant workflow regression, returning a final block or unblock decision for the release candidate.

Why does automated acceptance gating produce traceable outcomes for release candidates?▼

Acceptance gating produces traceable outcomes by explicitly reporting tested artifacts and pass or fail results, ensuring teams know exactly which checks blocked or unblocked the release.