Setting the file. One moment.
Subchapter 1.2
roll.mdMarkdown2 KBView on GitHub
Obtain latest Playwright version
npm info playwright@next version
Update Playwright packages in package.json:
playwright and playwright-core (dependencies) and @playwright/test (devDependency) to the target version.npm install to update package-lock.json.npm ls playwright-core that the root playwright-core actually rolled — it is pinned directly in package.json and is what playwright-cli.js runs; forgetting it leaves the CLI on the old version while tests pass against the new @playwright/test.Run the update script to sync skills and README:
node scripts/update.jsThis script:
node playwright-cli.js install --skills to regenerate skills from the new Playwright version..claude/skills/playwright-cli/ into skills/playwright-cli/..claude/skills/ directory.Update README.md with relevant changes from the updated skill at skills/playwright-cli/SKILL.md. Compare the skill file with the README and update any sections that are out of date (commands, flags, default behaviors, examples).
Verify the CLI works:
node playwright-cli.js --helpTest the CLI:
npm run testCreate a branch and commit:
roll_<version> (e.g. roll_214)chore: roll Playwright to <version>| File | Role |
|---|---|
package.json | Playwright version pins (playwright, @playwright/test) |
playwright-cli.js | CLI entry point — requires Playwright’s program module |
scripts/update.js | Automation script for syncing skills and README after version bump |
skills/playwright-cli/SKILL.md | Skill definition installed from Playwright (source of truth for commands) |
README.md | User-facing docs — must reflect current skill commands and behavior |