playwright-java-release Skill
Prepare a Playwright Java release after the rolling PR has merged — cut the release branch, mark the Maven version, draft the GitHub release, and tick the Java boxes in the internal checklist. Published by microsoft in playwright-java.
Decision snapshot
Is this a fit?
Browser automation, Research, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is playwright-java-release Skill?
Prepare a Playwright Java release after the rolling PR has merged — cut the release branch, mark the Maven version, draft the GitHub release, and tick the Java boxes in the internal checklist. Published by microsoft in playwright-java. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Research
- Browser automation use cases
- Research use cases
Declared skill metadata
- Source file: .claude/skills/playwright-java-release/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use playwright-java-release Skill
- Use it for browser automation.
- Use it for research.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/playwright-java
- Skill file: .claude/skills/playwright-java-release/SKILL.md
What it does
Prepare a Playwright Java release after the rolling PR has merged — cut the release branch, mark the Maven version, draft the GitHub release, and tick the Java boxes in the internal checklist.
Skill instructions
Use this skill once the chore: roll driver to 1.X.0 PR has merged into main and the upstream JS v1.X.0 is published. The rolling work itself is covered by the [[playwright-roll]] skill. Throughout this doc, replace X with the minor version (e.g. 60 for 1.60.0) and <user with the fork owner (gh api user --jq .login). The full release checklist lives in the private microsoft/playwright-internal repo as the v1.X checklist issue. Find its number once: bash unset GITHUBTOKEN ISSUE=$(gh search issues --repo microsoft/playwright-internal "v1.X checklist" --json number --jq '.[0].number') Tick each Java box incrementally (one PATCH per item) so the issue reflects accurate state if the flow is interrupted: bash gh api repos/microsoft/playwright-internal/issues/$ISSUE --jq '.body' /tmp/body.md edit /tmp/body.md to flip "- [ ]" → "- [x]" on the relevant Java item gh api repos/microsoft/playwright-internal/issues/$ISSUE -X PATCH --field body=@/tmp/body.md 1. Cut the release branch Push release-1.X
Verified compatibility and discovery
Frequently asked questions
What is playwright-java-release?
playwright-java-release is a open-source AI agent skill with Copy skill directory. Prepare a Playwright Java release after the rolling PR has merged — cut the release branch, mark the Maven version, draft the GitHub release, and tick the Java boxes in the internal checklist.
Who is playwright-java-release best for?
playwright-java-release is best for reusing agent instructions, scripts, and references, browser automation workflows, research workflows.
How do I install playwright-java-release?
Install or run playwright-java-release using Copy skill directory. Check playwright-java-release for the latest setup command.
Is playwright-java-release actively maintained?
playwright-java-release may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
