Review And Fix
hmislk/hmis
Deep-review one open PR, apply the resulting fixes, verify each one live (build → local redeploy → Playwright + DB), commit, push, drive CI to green, then reply to the review threads.
Agent skill
Playwright Java QA Review
by Tahanima in Tahanima/playwright-java-test-automation-architecture
Reviews Playwright-Java test code in phases, checking page-object architecture, then using a Playwright MCP tool to verify shaky locators live.
Install Playwright Java QA Review
$ npx skills add Tahanima/playwright-java-test-automation-architecture --skill code-reviewer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Tahanima/playwright-java-test-automation-architecture code-reviewer --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/Tahanima/playwright-java-test-automation-architecture.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.gemini/skills/code-reviewer .claude/skills/code-reviewer && 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 "code-reviewer" agent skill from https://github.com/Tahanima/playwright-java-test-automation-architecture/tree/main/.gemini/skills/code-reviewer into .claude/skills/code-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-reviewer", 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/Tahanima/playwright-java-test-automation-architecture/tree/main/.gemini/skills/code-reviewerType 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 Tahanima/playwright-java-test-automation-architecture --skill code-reviewer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Tahanima/playwright-java-test-automation-architecture code-reviewer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Tahanima/playwright-java-test-automation-architecture.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.gemini/skills/code-reviewer .agents/skills/code-reviewer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "code-reviewer" agent skill from https://github.com/Tahanima/playwright-java-test-automation-architecture/tree/main/.gemini/skills/code-reviewer into .agents/skills/code-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-reviewer", 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 Tahanima/playwright-java-test-automation-architecture --skill code-reviewer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Tahanima/playwright-java-test-automation-architecture code-reviewer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Tahanima/playwright-java-test-automation-architecture.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.gemini/skills/code-reviewer .cursor/skills/code-reviewer && 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 "code-reviewer" agent skill from https://github.com/Tahanima/playwright-java-test-automation-architecture/tree/main/.gemini/skills/code-reviewer into .cursor/skills/code-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-reviewer", 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/Tahanima/playwright-java-test-automation-architecture.git --path .gemini/skills/code-reviewer--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 Tahanima/playwright-java-test-automation-architecture --skill code-reviewer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Tahanima/playwright-java-test-automation-architecture code-reviewer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Tahanima/playwright-java-test-automation-architecture.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.gemini/skills/code-reviewer .gemini/skills/code-reviewer && 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 "code-reviewer" agent skill from https://github.com/Tahanima/playwright-java-test-automation-architecture/tree/main/.gemini/skills/code-reviewer into .gemini/skills/code-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-reviewer", 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 Tahanima/playwright-java-test-automation-architecture code-reviewerInstalls 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 Tahanima/playwright-java-test-automation-architecture --skill code-reviewer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Tahanima/playwright-java-test-automation-architecture.git skills-src && mkdir -p .github/skills && cp -r skills-src/.gemini/skills/code-reviewer .github/skills/code-reviewer && 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 "code-reviewer" agent skill from https://github.com/Tahanima/playwright-java-test-automation-architecture/tree/main/.gemini/skills/code-reviewer into .github/skills/code-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-reviewer", 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 Tahanima/playwright-java-test-automation-architecture --skill code-reviewer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Tahanima/playwright-java-test-automation-architecture code-reviewer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Tahanima/playwright-java-test-automation-architecture.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.gemini/skills/code-reviewer .opencode/skills/code-reviewer && 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 "code-reviewer" agent skill from https://github.com/Tahanima/playwright-java-test-automation-architecture/tree/main/.gemini/skills/code-reviewer into .opencode/skills/code-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-reviewer", 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
code-reviewer- GitHub stars
- 113
- Token cost
- ~561 tokens
- SKILL.md length
- 255 words
- Files
- 2
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Reviews Playwright-Java test code in phases, checking page-object architecture, then using a Playwright MCP tool to verify shaky locators live.
- Works in 3 steps: Multi-Step Review Process → Refactoring Standards → Reference Material
- Reviewing a Playwright-Java pull request before merge
- SKILL.md covers 1. Multi-Step Review Process, 2. Refactoring Standards and 3. Reference Material
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill reviews Playwright-Java test automation in three phases, starting with the file's architectural role: whether it is a page or component that must extend a base class with private locators, a test-data class that wraps CSVs without instantiating pages directly, or an end-to-end test that extends a base test class with the right annotations.
When a new or fragile-looking locator appears, especially one skipping accessibility roles, it moves to live checking: calling a Playwright MCP tool to open the target page and compare the real accessibility tree against the proposed locator. Feedback comes back marked as a violation, a minor improvement, or correct work, cross-referenced against the project's own written review rules.
When your agent uses it
- Reviewing a Playwright-Java pull request before merge
- Checking whether new locators follow accessibility-role conventions
- Verifying a page object's fluent interface and package structure
Example prompts
- “Review this new LoginPage class against our review rules.”
- “Check if this test's locators will hold up against the live DOM.”
- “Does this page object follow our standard package structure?”
Requirements
- A Playwright MCP tool connection for live locator checks
Workflow steps
3 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 b94e336. 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
Playwright Java QA Review loads about 561 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 255 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 Tahanima/playwright-java-test-automation-architecture at commit b94e336, republished under its MIT licence (© Tahanima). 255 words, ~561 tokens.
Download SKILL.mdSave it as
.claude/skills/code-reviewer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- code-reviewer
- description
- Acts as a Senior QA Lead to review Playwright-Java code, ensuring architectural integrity and test stability using static analysis and live MCP verification.
Senior QA Lead - Code Review Instructions
You are a Senior QA Automation Lead specializing in the Playwright-Java ecosystem. Your goal is to ensure that code is not only syntactically correct but architecturally sound and stable.
1. Multi-Step Review Process
Phase 1: Static Architectural Analysis
Determine the file's role based on the project path:
- Pages/Components: Check for
BasePage/BaseComponentinheritance and private locators. - TestData: Ensure it acts as a POJO/Logic wrapper for CSVs and avoids direct Page instantiation.
- E2E Tests: Verify
BaseTestinheritance and mandatory Allure/Category annotations.
Phase 2: Live Validation (Tool Use)
When the code introduces new locators or complex UI interactions:
- Trigger: Use the
@playwrightMCP tool if you identify "brittle" or suspicious locators (e.g., those not using accessibility roles). - Action: Use
playwright_navigateto visit the target URL (derived frompage.navigatelogic) and verify the DOM structure. - Verification: Ensure that proposed
AriaRolechoices match the actual accessibility tree of the application.
Phase 3: Feedback & Refactoring
Provide feedback in the following format:
- ❌ Violation: Serious architectural flaws, hardcoded data, or locators that fail live verification.
- ⚠️ Improvement: Minor code smells, missing Fluent interface returns, or optimization opportunities.
- ✅ Correct: Praise for clean implementation and strict adherence to the
io.github.tahanimastandard.
2. Refactoring Standards
When providing corrected code:
- Package Integrity: Always maintain the
io.github.tahanimapackage structure. - Framework Alignment: Use
ConfigurationManager.configuration()for settings andAllureManagerfor logging. - Fluent Interface: Ensure Page Object methods return
thisor the next Page instance to support method chaining.
3. Reference Material
Always cross-reference your findings with the specific rules defined in review-rules.md.
© Tahanima, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .gemini/skills/code-reviewer of Tahanima/playwright-java-test-automation-architecture.
- SKILL.md
- review-rules.md
Open the folder on GitHubat commit b94e336
Compare with similar skills
Playwright Java QA 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 |
|---|---|---|---|---|---|---|
| Playwright Java QA Review this skillTahanima/playwright-java-test-automation-architecture | 113 | — | ~561 | Automated safety check: Pass | MIT | |
| Review And Fixhmislk/hmis | 236 | — | ~4.9k | Automated safety check: Pass | GPL-3.0 | |
| Playwright Rollmicrosoft/playwright-dotnet | 3k | — | ~1.9k | Automated safety check: Pass | MIT | |
| API Testingfugazi/test-automation-skills-agents | 247 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Bangle Followup Operatorbangle-io/bangle-io | 1.2k | — | ~991 | Automated safety check: Pass | AGPL-3.0 | |
| Webapp Selenium Testingfugazi/test-automation-skills-agents | 247 | — | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
- Official
Playwright Roll
microsoft/playwright-dotnet
Roll Playwright .NET to a new version
API Testing
fugazi/test-automation-skills-agents
Test REST and GraphQL endpoint contracts using Playwright request fixture (TypeScript) or REST Assured (Java).
Bangle Followup Operator
bangle-io/bangle-io
Operate recurring Bangle.io agent follow-ups after a thread has already started.
Webapp Selenium Testing
fugazi/test-automation-skills-agents
Author and maintain versioned Selenium WebDriver tests with Java and JUnit 5.
QA
Kiln-AI/Kiln
Multi-agent, browser-driven QA pass over a branch or PR — scope it, plan it, fan out one subagent per testing area in its own isolated sandbox, compile a severity-ranked markdown report.
More from Tahanima/playwright-java-test-automation-architecture
Playwright Healing Agent
Tahanima/playwright-java-test-automation-architecture
Expert in diagnosing Playwright failures. Uses the @playwright MCP to verify live DOM state.
Related
Works with
Categories
Questions about Playwright Java QA Review
What does Playwright Java QA Review do?
Reviews Playwright-Java test code in phases, checking page-object architecture, then using a Playwright MCP tool to verify shaky locators live. This skill reviews Playwright-Java test automation in three phases, starting with the file's architectural role: whether it is a page or component that must extend a base class with private locators, a test-data class that wraps CSVs without instantiating pages directly, or an end-to-end test that extends a base test class with the right annotations.
When should I use Playwright Java QA Review?
Playwright Java QA Review fits situations like: reviewing a Playwright-Java pull request before merge; checking whether new locators follow accessibility-role conventions; verifying a page object's fluent interface and package structure.
How do I install Playwright Java QA Review in Claude Code?
Run `npx skills add Tahanima/playwright-java-test-automation-architecture --skill code-reviewer -a claude-code`. Or copy the skill folder (.gemini/skills/code-reviewer in Tahanima/playwright-java-test-automation-architecture) into .claude/skills/code-reviewer in your project. Claude Code loads it when a task matches its description.
How do I install Playwright Java QA Review in Codex?
Run `npx skills add Tahanima/playwright-java-test-automation-architecture --skill code-reviewer -a codex`. Or copy the skill folder (.gemini/skills/code-reviewer in Tahanima/playwright-java-test-automation-architecture) into .agents/skills/code-reviewer in your project. Codex loads it when a task matches its description.
Can I use Playwright Java QA 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 Tahanima/playwright-java-test-automation-architecture --skill code-reviewer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-reviewer, .gemini/skills/code-reviewer, .github/skills/code-reviewer and .opencode/skills/code-reviewer in your project.
What does Playwright Java QA Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Playwright Java QA Review is instructions for the agent only. Our summary lists: A Playwright MCP tool connection for live locator checks.
Does Playwright Java QA 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 Playwright Java QA 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 Playwright Java QA Review use?
Playwright Java QA Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Playwright Java QA Review use?
About 561 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 Playwright Java QA Review?
Skills that share tags, products or a category with Playwright Java QA Review: Review And Fix (hmislk/hmis, 236 stars), Playwright Roll (microsoft/playwright-dotnet, 3k stars), API Testing (fugazi/test-automation-skills-agents, 247 stars) and Bangle Followup Operator (bangle-io/bangle-io, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Playwright Java QA Review?
Tahanima (a GitHub user) maintains it in Tahanima/playwright-java-test-automation-architecture, which has 113 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on February 23, 2026.
Source: Tahanima/playwright-java-test-automation-architecture on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.