Borrowing it
Nothing to install: this file belongs to Tahanima/playwright-java-test-automation-architecture. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Tahanima/playwright-java-test-automation-architecture/main/.gemini/skills/code-reviewer/SKILL.mdgit clone --depth 1 https://github.com/Tahanima/playwright-java-test-automation-architectureWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/tahanima/playwright-java-test-automation-architecture/code-reviewer)<a href="https://agentmods.dev/skills/tahanima/playwright-java-test-automation-architecture/code-reviewer"><img src="https://agentmods.dev/badge/skills/tahanima/playwright-java-test-automation-architecture/code-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tahanima/playwright-java-test-automation-architecture/code-reviewer"><img src="https://agentmods.dev/badge/skills/tahanima/playwright-java-test-automation-architecture/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00032 | $0.00484 |
| Opus 5.5 | $0.00013 | $0.00194 |
| Sonnet 5.5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
code-reviewer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 38 lines · 32 tokens per session scan A 71aa56de5b2e
code-reviewer is a skill published in the GitHub repository Tahanima/playwright-java-test-automation-architecture (114 stars, last pushed 8mo ago), licensed MIT. It adds 32 tokens to every session and 484 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
shaft-developer
Use when starting any SHAFT testing task to select exactly one lifecycle, implementation, or tool specialist before doing the work.
shaft-test-case-design
Use when designing reviewable test cases or scenarios with traceability, data, steps, expected results, techniques, priorities, and boundary coverage.
shaft-accessibility-testing
Use when testing web or mobile accessibility for WCAG conformance, keyboard and focus behavior, semantics, errors, or user impact.
shaft-api-testing
Use when implementing or repairing SHAFT.API tests for HTTP requests, authentication, payloads, schemas, responses, contracts, or service workflows.
shaft-automated-test-authoring
Use when implementing or repairing executable SHAFT Java tests for web, mobile, API, database, CLI, TestNG, JUnit, or Cucumber behavior.
shaft-change-verification
Use when edited SHAFT Java needs a reuse plan, preview diff, guardrail check, approved application, focused test, and evidence-backed verdict.