Pre Release Sweep
LanternOps/breeze
Use before cutting a Breeze release, or whenever asked to "test everything since the last release", "check what's changed on main in the browser", "boot the stack and verify the merged PRs", or…
Verify UI/UX by running Playwright tests and reviewing screenshots.
Install UI Review
$ npx skills add jvm-skills/jvm-skills --skill ui-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jvm-skills/jvm-skills ui-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jvm-skills/jvm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.junie/skills/ui-review .claude/skills/ui-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ui-review" agent skill from https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/ui-review into .claude/skills/ui-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/ui-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jvm-skills/jvm-skills --skill ui-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jvm-skills/jvm-skills ui-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jvm-skills/jvm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.junie/skills/ui-review .agents/skills/ui-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ui-review" agent skill from https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/ui-review into .agents/skills/ui-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jvm-skills/jvm-skills --skill ui-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jvm-skills/jvm-skills ui-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jvm-skills/jvm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.junie/skills/ui-review .cursor/skills/ui-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ui-review" agent skill from https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/ui-review into .cursor/skills/ui-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jvm-skills/jvm-skills.git --path .junie/skills/ui-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jvm-skills/jvm-skills --skill ui-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jvm-skills/jvm-skills ui-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jvm-skills/jvm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.junie/skills/ui-review .gemini/skills/ui-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ui-review" agent skill from https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/ui-review into .gemini/skills/ui-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jvm-skills/jvm-skills ui-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jvm-skills/jvm-skills --skill ui-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jvm-skills/jvm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.junie/skills/ui-review .github/skills/ui-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ui-review" agent skill from https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/ui-review into .github/skills/ui-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jvm-skills/jvm-skills --skill ui-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jvm-skills/jvm-skills ui-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jvm-skills/jvm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.junie/skills/ui-review .opencode/skills/ui-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ui-review" agent skill from https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/ui-review into .opencode/skills/ui-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ui-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ui-review- GitHub stars
- 139
- Token cost
- ~545 tokens
- SKILL.md length
- 198 words
- Files
- 1
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Verify UI/UX by running Playwright tests and reviewing screenshots.
- Works in 4 steps: Identify what to review → Run tests to generate screenshots → Review screenshots → …
- You want to check that a page looks correct and the user flow works — after implementing UI changes
- SKILL.md covers Process and Project Customization
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
UI Review is an agent skill from jvm-skills/jvm-skills. Verify UI/UX by running Playwright tests and reviewing screenshots. Use when you want to check that a page looks correct and the user flow works — after implementing UI changes, fixing visual bugs, or verifying an existing page. Triggers: 'check the UI', 'does this page look right', 'verify the layout', 'review screenshots', 'run UI tests'.
Its SKILL.md is about 550 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering UI design, UX design and Browser testing. It works with Playwright. The licence is Apache-2.0.
When your agent uses it
- You want to check that a page looks correct and the user flow works — after implementing UI changes
- Fixing visual bugs
- Verifying an existing page
Example prompts
- “check the UI”
- “does this page look right”
- “verify the layout”
- “/ui-review”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit c6d477f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
UI Review loads about 545 tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 198 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jvm-skills/jvm-skills at commit c6d477f, republished under its Apache-2.0 licence (© jvm-skills). 198 words, ~545 tokens.
Download SKILL.mdSave it as
.claude/skills/ui-review/SKILL.md (or your agent's skills folder).- name
- ui-review
- description
- Verify UI/UX by running Playwright tests and reviewing screenshots. Use when you want to check that a page looks correct and the user flow works — after implementing UI changes, fixing visual bugs, or verifying an existing page. Triggers: 'check the UI', 'does this page look right', 'verify the layout', 'review screenshots', 'run UI tests'.
- dependencies
- test
- agents
- ui-review
UI Review
Run Playwright tests to generate fresh screenshots, then review them for UI/UX correctness.
Process
1. Identify what to review
Determine which page/component to verify. The user may specify:
- A test class name (e.g.
*LoginTest) - A page or component name (search for the corresponding Playwright test)
- A screenshot folder to review directly (skip to step 3)
2. Run tests to generate screenshots
Run the relevant Playwright test(s) to produce fresh screenshots. Check references/project.md for the exact test command and flags. If no project overlay exists, run:
/test *TestClassNameIf no Playwright test exists for this page, tell the user — don't silently skip.
3. Review screenshots
Spawn the ui-review subagent on the screenshot folder. Provide:
- The screenshot path (check
references/project.mdfor the convention, or search for the test's screenshot output) - The expected flow: what each step should show, what the user should see
Agent(subagent_type="ui-review", prompt="Review screenshots for UI/UX correctness.
Screenshots: <screenshot-path>
Test: '<test name>'
Purpose: <what this test verifies>
Expected flow:
- 01: <what should be visible>
- 02: <next step>
- ...
Flag any problems: broken layouts, blank pages, missing elements, bad UX flow.")4. Report and fix
- If the subagent reports problems, fix them and re-run (go back to step 2)
- If everything looks good, report confirmation to the user
Project Customization
Read references/project.md in this skill's directory if it exists. It provides project-specific context:
- Test command and flags for headless Playwright
- Screenshot output directory convention
- Any other project-specific patterns
© jvm-skills, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .junie/skills/ui-review of jvm-skills/jvm-skills.
Open the folder on GitHubat commit c6d477f
Compare with similar skills
UI Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| UI Review this skilljvm-skills/jvm-skills | 139 | — | ~545 | Automated safety check: Pass | Apache-2.0 | |
| Pre Release SweepLanternOps/breeze | 132 | — | ~2.6k | Automated safety check: Notes | AGPL-3.0 | |
| Liteyuki Webui FrontendLiteyukiStudio/LiteyukiBot | 157 | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| UI QA SweepLanternOps/breeze | 132 | — | ~3k | Automated safety check: Notes | AGPL-3.0 | |
| E2Eopenathleteorg/openathlete | 101 | — | ~699 | Automated safety check: Pass | AGPL-3.0 | |
| Playwright E2E Testingfugazi/test-automation-skills-agents | 249 | — | ~3.2k | Automated safety check: Pass | MIT |
Similar skills
Liteyuki Webui Frontend
LiteyukiStudio/LiteyukiBot
Build, review, or test LiteyukiBot v7's React/Vite WebUI under webui/ and its packaged static delivery in packages/webui/.
UI QA Sweep
LanternOps/breeze
Broad regression QA of the Breeze RMM web UI via Playwright — exercising everyday MSP workflows and setup tasks like a human QA tester, logging functional PASS/FAIL plus UI/UX observations, and…
E2E
openathleteorg/openathlete
Run, debug or extend the OpenAthlete Playwright end-to-end tests, which exercise the production Docker images (API, worker, web, PostgreSQL, Redis) through the API and a real browser on desktop and…
Playwright E2E Testing
fugazi/test-automation-skills-agents
Author and maintain versioned Playwright (@playwright/test) TypeScript UI specs for browser user flows.
Webapp Testing
flonat/flonat-research
Exercise and verify a local web application through Playwright, including user flows and rendered behaviour.
More from jvm-skills/jvm-skills
All 16 skills in this repoMutation Testing
jvm-skills/jvm-skills
Bootstrap pitest via the info.solidsoft.pitest Gradle plugin with Kotlin-sane defaults, run mutation tests scoped to changed classes, interpret surviving mutants from mutations.xml, triage…
Ralph Coverage
jvm-skills/jvm-skills
Run Ralph in coverage mode — iteratively write tests for untested classes until coverage targets are met.
Skill Scout
jvm-skills/jvm-skills
Run the skill-scout loop — scan the next batch of unscanned JVM-conference rosters for speaker-created AI skills and apply results to the CSV store via the overnight Workflow.
Spec
jvm-skills/jvm-skills
Generate a feature spec with user stories directly from conversation context and codebase exploration — no interview needed.
Kotest
jvm-skills/jvm-skills
Write a new Kotlin test, or modernize an existing one, using Kotest matchers and idiomatic Kotlin test style — backticked names, apply/assertSoftly blocks, and existing object mothers and helpers.
Voice
jvm-skills/jvm-skills
Make prose sound like Thomas, not like a generic technical writer.
Related
Works with
Categories
Questions about UI Review
What does UI Review do?
Verify UI/UX by running Playwright tests and reviewing screenshots. UI Review is an agent skill from jvm-skills/jvm-skills. Verify UI/UX by running Playwright tests and reviewing screenshots.
When should I use UI Review?
UI Review fits situations like: you want to check that a page looks correct and the user flow works — after implementing UI changes; fixing visual bugs; verifying an existing page.
How do I install UI Review in Claude Code?
Run `npx skills add jvm-skills/jvm-skills --skill ui-review -a claude-code`. Or copy the skill folder (.junie/skills/ui-review in jvm-skills/jvm-skills) into .claude/skills/ui-review in your project. Claude Code loads it when a task matches its description.
How do I install UI Review in Codex?
Run `npx skills add jvm-skills/jvm-skills --skill ui-review -a codex`. Or copy the skill folder (.junie/skills/ui-review in jvm-skills/jvm-skills) into .agents/skills/ui-review in your project. Codex loads it when a task matches its description.
Can I use UI Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jvm-skills/jvm-skills --skill ui-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ui-review, .gemini/skills/ui-review, .github/skills/ui-review and .opencode/skills/ui-review in your project.
What does UI Review need to run?
SKILL.md names no scripts, command-line tools or credentials: UI Review is instructions for the agent only.
Does UI Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is UI Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does UI Review use?
UI Review is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does UI Review use?
About 545 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to UI Review?
Skills that share tags, products or a category with UI Review: Pre Release Sweep (LanternOps/breeze, 132 stars), Liteyuki Webui Frontend (LiteyukiStudio/LiteyukiBot, 157 stars), UI QA Sweep (LanternOps/breeze, 132 stars) and E2E (openathleteorg/openathlete, 101 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains UI Review?
jvm-skills (a GitHub organization) maintains it in jvm-skills/jvm-skills, which has 139 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on August 31, 2026.
Source: jvm-skills/jvm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.