Run LLM-piloted Playwright smoke tests against deployed applications.
npx skills add https://github.com/Levezze/devkit --skill e2e-playwright-test
Please help me install this Agent Skill. Skill: e2e-playwright-test Source: https://github.com/Levezze/devkit/tree/main/skills/e2e-playwright-test Command: npx skills add https://github.com/Levezze/devkit --skill e2e-playwright-test
This Skill helps you validate a deployed app end-to-end without brittle tests by driving Playwright through an LLM-piloted checklist that can adapt to UI drift.
docs/guides/e2e-playwright-test.md, and on subsequent runs it improvises equivalent actions while recording drift updates.Run the skill to validate the deployed flow with a specific environment by asking your assistant to start e2e-playwright-test against --demo.
High-intent search queries and answers about installing and using this skill.
Run LLM-piloted e2e smoke tests against a deployed app by driving Playwright MCP using a repo checklist. The flow adapts to UI drift by improvising equivalent actions while recording updates for subsequent runs.
LLM-piloted Playwright testing works by executing a repo-specific operational checklist against real user paths like onboarding and questionnaire completion. It drives the Playwright MCP to navigate deployed environments and validates subsequent journey steps.
Yes, Playwright MCP availability is required to run these e2e smoke tests. You also need a working docs guide at docs/guides/e2e-playwright-test.md, with optional bootstrapping via /grill-me to populate missing checklist slots.
Yes, but the e2e smoke test applies safety guardrails for production environments. It requires explicit confirmation before any browser action in prod to avoid impacting real users and real billing flows.
Use the e2e-playwright-test skill with arg parsing for env/user/record-only to validate onboarding, questionnaire completion, and subsequent journey steps. It applies to demo, dev, local, and prod flow validation against deployed apps.
Brittle e2e tests break when UI changes are not handled, but drift-aware reporting with fail-stop on genuine breaks helps. It produces a step-by-step pass/drift/fail report including console errors, network deviations, and screenshot/DOM evidence on failure.
Ben2pcPersist Feishu app credentials and channel access policies to local environment files.
jeremylongshoreDetect infrastructure drift between current state and desired configuration.
sunholo-dataAutomates end-to-end AILANG release management including pre-release checks, version bumps, changelog updates, git tagging, CI/CD verification, and release broadcasting.
mattbutlerengineeringScaffold Playwright E2E spec files with app-specific auth fixtures.