oa-playwright-cli

oa-playwright-cli

An OpenAustria workflow skill for Claude Code that builds and maintains Playwright end-to-end test coverage with maximum agent autonomy, sitting on top of the upstream microsoft/playwright-cli tool and its bundled reference skill.

What it does

• Secures every UI feature with a persisted Playwright test. Not a one-shot browser interaction — a real test that keeps running on every build.
• Discovers swimlanes. For any feature, Claude enumerates the user-visible flows (login, create-todo, share-report, …) and checks coverage before writing anything.
• Drives playwright-cli to harvest semantic locators. Every CLI action prints the equivalent Playwright code; those lines become the test body, already using role-based locators that survive refactors.
• Wires tests into the project's native build. One command (mvn verify, ./gradlew check, npm test, pytest, make e2e) runs everything on CI.
• Covers the stacks OpenAustria actually uses: Java + Maven, Java + Gradle, Java + Spring Boot (primary), Node (npm/pnpm/yarn), Python (pytest-playwright), Flutter Web (with the semantics-tree caveat), and points you at integration_test for native Flutter.
• Debugs failures via the playwright-cli attach loop — distinguishes wrong locator, wrong timing, wrong assumption, and real bugs, and has a fix pattern for each.

Install

Option A — Claude Code marketplace (recommended)

Add the repo as a marketplace, then install the plugin. From inside Claude Code:

/plugin marketplace add martinvidec/oa-playwright-cli-skill
/plugin install oa-playwright-cli@oa-skills
/plugin install oa-playwright-cli@oa-skills --scope project   # if you want it shared with the team via VCS

Then reload if you installed mid-session:

/reload-plugins

The skill auto-activates when Claude detects a UI task that matches its description (new/changed UI feature, missing E2E coverage, failing Playwright tests, wiring tests into a build).

Option B — manual install (DIY script)

For users who do not want to use the marketplace system — or for CI provisioning — clone the repo and run install.sh:

git clone https://github.com/martinvidec/oa-playwright-cli-skill.git
cd oa-playwright-cli-skill
bash install.sh --scope user                 # installs to ~/.claude/skills/oa-playwright-cli/
# or
bash install.sh --scope project --target /path/to/your/project
# or
bash install.sh --scope project              # when run from inside the target project

Scopes:

• user — installs to ~/.claude/skills/oa-playwright-cli/. Available in every project on your machine.
• project — installs to <project>/.claude/skills/oa-playwright-cli/. Scoped to one project; commit it if your team should share the skill.

Run bash install.sh --help for all options including --force (overwrite existing install) and --dry-run (show what would happen without touching the filesystem).

Option C — git submodule

For projects that want to track this skill as a submodule and pin a commit:

cd /path/to/your/project
git submodule add https://github.com/martinvidec/oa-playwright-cli-skill.git .claude/skills/_upstream/oa-playwright-cli-skill
ln -s _upstream/oa-playwright-cli-skill/skills/oa-playwright-cli .claude/skills/oa-playwright-cli

Requirements

• Claude Code 1.x or newer (for marketplace install). Manual install works with any version that recognises ~/.claude/skills/.
• Node.js >= 18 (for playwright-cli — the skill offers to install it on first use).
• Project build system — one of: Maven, Gradle, npm/pnpm/yarn, Python (pyproject/setup.py/tox), or Flutter. The skill's preflight auto-detects and picks the right reference file.

The skill does not install Node.js or your build tools for you. It detects them and asks if you want to install playwright-cli itself.

Structure