acceptance

Automate Playwright browser acceptance sweeps with self-healing loops for OmegaOS deployments.

10|3|Updated May 26, 2026

Search Tags:#automation #playwright #e2e-testing #browser #acceptance #clerk-auth #self-heal

Ready to run

npx skills add https://github.com/agentik-os/OmegaOS --skill acceptance-agentik-os

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acceptance
Source: https://github.com/agentik-os/OmegaOS/tree/main/skills/acceptance
Command: npx skills add https://github.com/agentik-os/OmegaOS --skill acceptance-agentik-os

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OmegaOS automated browser acceptance and self-heal gate validates that builds are truly working by sweeping all routes in a running app, capturing console errors and failing network requests, and autonomously fixing issues to re-run until green.

Core Features & Use Cases

Autonomous end-to-end browser acceptance sweeps using Playwright across all routes.
Self-healing loop that fixes root causes (missing routes, auth issues, console/network errors) and replays sweeps.
Validates authenticated golden paths and persists actions across reloads to ensure real backend writes.

Quick Start

Run the acceptance sweep in your project directory to validate the running app and automatically heal failures.

Frequently Asked Questions about acceptance

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

FAQPage Schema

How do I automate end-to-end acceptance testing with Playwright across all routes?▼

Automated end-to-end acceptance testing with Playwright sweeps all routes in a running app to capture console errors and failing network requests, looping until a green sweep or a blocker is encountered.

What is browser acceptance self-healing and how does it fix failing e2e tests?▼

Browser acceptance self-healing autonomously fixes root causes like missing routes, auth issues, and console or network errors, then replays the Playwright sweeps until the build passes.

Can I validate Clerk authenticated workflows and persist writes across reloads in e2e tests?▼

You can validate Clerk authenticated workflows by providing credentials to log in, verifying logged-in paths, and confirming that core actions persist across reloads for real backend writes.

Does the acceptance gate require a running app environment to test route sweeps?▼

The acceptance gate requires a running app in your project directory to perform route sweeps, validate authenticated paths, and report whether builds render cleanly.

Why does my automated browser acceptance sweep loop instead of passing on the first run?▼

The automated browser acceptance sweep loops to apply self-healing fixes to root causes like console errors and missing routes, replaying tests until a green sweep is achieved.

Best way to gate OmegaOS deployments for green builds using browser automation?▼

Gating OmegaOS deployments for green builds uses autonomous Playwright browser automation to sweep routes, validate authenticated workflows, and self-heal failures until the build passes.