test-review

test-review is a skill for Claude Code from akovalion/paranoid-qa. It costs 137 tokens per session (7,617 once invoked), scanned A, original, MIT.

A review checklist for newly written or changed automated tests using TypeScript and Playwright. Playwright is a tool for testing web browsers, and automated tests check software without repeating the steps by hand.

In plain words
What is it for?
Use it to review UI, API, combined UI-and-API, visual, mobile, mock, Page Object, and fixture changes against Playwright guidance and project conventions.
Why use it?
It finds problems in test code before they make the test suite unreliable or difficult to maintain.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md.

Part of the paranoid-qa-ru plugin — 5 skills shipped together

Good fit Use it to review UI, API, combined UI-and-API, visual, mobile, mock, Page Object, and fixture changes against Playwright guidance and project conventions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/akovalion/paranoid-qa/test-review
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add akovalion/paranoid-qa --skill test-review
Clone the repo
git clone --depth 1 https://github.com/akovalion/paranoid-qa

Made for: Claude Code.

Or install paranoid-qa-ru, the plugin that ships this one along with the rest of its 5 skills.

Wrote 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.

agentmods badge for test-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/akovalion/paranoid-qa/test-review/github.svg)](https://agentmods.dev/skills/akovalion/paranoid-qa/test-review)
Your own site
<a href="https://agentmods.dev/skills/akovalion/paranoid-qa/test-review"><img src="https://agentmods.dev/badge/skills/akovalion/paranoid-qa/test-review/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.

agentmods 80×15 button for test-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/akovalion/paranoid-qa/test-review"><img src="https://agentmods.dev/badge/skills/akovalion/paranoid-qa/test-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 137 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,617 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium analysis-evasion · line 1
    Suspicious Unicode normalization or mixed-script content
    Fix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
  • medium MCP Rug Pull · line 47
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00137 $0.07617
Opus 5.5 $0.00055 $0.03047
Sonnet 5.5 $0.00027 $0.01523
Haiku 4.5 $0.00014 $0.00762

Measured 3d ago against content hash f3dd175d562b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

test-review 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 3d 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.

ru/skills/test-review/SKILL.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ревью автотестов (TypeScript + Playwright)

Проверь только что написанный или изменённый тест-код на соответствие best practices и выдай приоритизированный список замечаний с фиксами. Источник правил — официальная документация Playwright (best-practices, locators, test-assertions) и TypeScript + конвенции конкретного проекта.

Источник правды по проекту — его корневой CLAUDE.md (если есть) и стиль соседнего кода. Этот скилл — фаза проверки: он дополняет проектные правила, не заменяет их. Развёрнутые ❌ до → ✅ после и ссылки на источники по каждому правилу — в references/rules-catalog.md.


Ты - независимый ревьюер. Истории сессии, где писали код, у тебя нет, и это намеренно: ревьюер, который видел, почему принято каждое решение, склонен с ними соглашаться. Оценивай код как он есть, без объяснений автора.

Scope от вызывающего: $ARGUMENTS

Когда применять и режим работы

  • Только диагностика. Прочитать код, прогнать статический анализ, выдать отчёт. Файлы не правишь: отчёт уходит вызывающей сессии, фиксы применяет она.
  • Первым делом прочитай корневой CLAUDE.md проекта (если есть): в изолированном контексте он может не подгрузиться.
  • Scope — только новое/изменённое, не весь suite. Пути из аргументов; без них - незакоммиченные изменения (git status + git diff).
  • Любой тип теста: UI E2E, API, UI+API, visual regression, mobile, моки, а также Page Object, фикстуры, константы.
  • Тесты прогоняешь только если об этом просят в аргументах. Весь suite и браузер - никогда.

Доказательная дисциплина (без галлюцинаций)

  • Каждое замечание — по реально прочитанной строке (file:line) или по наблюдённому выводу typecheck / lint / прогона. Не выдумывай нарушения «по аналогии» и не ссылайся на строки, которых не видел.
  • Правило проверяется инструментом (tsc, ESLint, прогон) → сначала запусти инструмент, потом репорти его вывод, а не «вероятно есть».
  • Не уверен, что это дефект, а не осознанное решение проекта → помечай «под вопросом», не утверждай. Сверяйся с CLAUDE.md проекта и соседним кодом: часть «анти-паттернов» может быть намеренной (легаси-хелперы, нестандартная разметка, осознанные исключения из правил). Имена файлов/эндпоинтов/селекторов из памяти и прошлого контекста — фон, перепроверяй на живом коде.
  • Решение, которое без объяснения автора выглядит нарушением, не угадывай и не оправдывай. Выноси его в «Под вопросом» с конкретным вопросом автору.
  • В отчёт - только прогоны, которые сделал сам.
  • Не нашёл нарушений в категории — так и пиши «чисто», не придумывай замечание ради объёма.

Read the full file on GitHub · 207 lines

Files

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.

Changes

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.

  1. 3d ago Changed · +7 lines f3dd175d562b
  2. 6d ago Changed · +2 lines 845805803f99
  3. 20d ago Changed · +14 lines · +18 tokens per session f865212a0f6b
  4. 1mo ago Changed ce266c4ffd93
  5. 1mo ago First seen · 184 lines · 119 tokens per session scan A 8de97a5cf7e1

Subscribe to this mod's changes

test-review is a skill published in the GitHub repository akovalion/paranoid-qa (16 stars, last pushed 3d ago), licensed MIT. It adds 137 tokens to every session and 7,617 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

mk:qa

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a…

ngocsangyem/MeowKit · 127 tokens

daa-review

Use when reviewing existing test code for DAA compliance, identifying anti-patterns, or suggesting improvements to automation test architecture.

gigayaya/DAA-Master · 26 tokens

qawolf-cli

Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; run or list flows…

qawolf/cli · 112 tokens

automated-e2e-testing

A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.

fishzjp/qa-skills · 112 tokens

e2e-reviewer

Use when reviewing Playwright or Cypress E2E specs, Page Objects (POM), PRs, pull requests, patches, diffs, or changed test files — asked to review tests, audit test quality, or find weak, flaky, or silently-passing tests; when tests pass CI but prove nothing or miss bugs; when auditing missing awaits, vacuous or…

voidmatcha/e2e-skills · 131 tokens

qa-expert

Expert-level quality assurance, testing strategies, automation, and QA processes. Use when the user mentions testing, test automation, quality assurance, or Selenium, or when the task involves Testing Types, QA Processes, Test Strategy, or Defect Management.

personamanagmentlayer/pcl · 53 tokens