Frontend Review Testing

Use when auditing test infrastructure — vitest coverage, playwright configuration, VRT setup, coverage merging. Produces recommendations for Week 2 testing phase. Runs `scripts/audit-coverage.sh`.

423 stars 6 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add mizchi/skills --skill frontend-review-testing
Manual install
git clone --depth 1 https://github.com/mizchi/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/frontend-review-testing ~/.claude/skills/frontend-review-testing

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Frontend Review — Testing

You are auditing the testing posture of a frontend project. The phase is Week 2: establish vitest + playwright with synthetic coverage, keeping in mind:

- **E2E granularity**: initially, one case per Router / server controller branch (skeleton-first, not exhaustive).
- **Unit granularity**: component coverage is prioritized.
- **Coverage merge**: vitest V8 + playwright V8 combined via `monocart-coverage-reports` or `istanbul-merge`.

## Procedure

Collector reports use a versioned envelope: read values under `data`, inspect `status` and `issues`, and keep missing measurements distinct from zero. See the local collection contract.

1. Run `scripts/audit-coverage.sh --repo <client-repo>`.
2. Read `coverage/coverage-summary.json` if it exists.
3. Inspect:
   - `vitest.config.*` — is coverage configured? provider v8?
   - `playwright.config.*` — projects, webServer, sharding
   - `tests/`, `e2e/`, `__tests__/` — current test count and shape
   - `package.json` scripts — `test`, `test:coverage`, `test:e2e`

## Output

Write `<client-repo>/.frontend-review/report/latest/md/testing-review.md` with:

- **Current state**: vitest configured? playwright configured? how many tests? what coverage %?
- **Gaps**: missing config, missing scripts, no coverage merge
- **Recommended PRs** (3-5 max): each with title, affected files, expected coverage delta
- **Branch coverage checklist** for the router/controller branches that should get the first E2E tests
Read the full skill on GitHub

Details

Skill name
frontend-review-testing
Repository
mizchi/skills
Path
frontend-review-testing/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Frontend Review Testing skill do?

Use when auditing test infrastructure — vitest coverage, playwright configuration, VRT setup, coverage merging. Produces recommendations for Week 2 testing phase. Runs `scripts/audit-coverage.sh`.

How do I install the Frontend Review Testing skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add mizchi/skills --skill frontend-review-testing. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Frontend Review Testing popular?

It lives in mizchi/skills, which has 423 GitHub stars and 6 forks.

Related skills

Actions CI Tuning

423

mizchi/skills

Use when auditing or improving GitHub Actions workflows for a project. Covers cache setup (npm/pnpm/yarn), job parallelism, shard-based test splitting, artifact handling pitfalls, and Playwright-specific patterns. Trigger on: slow CI, cache miss, flaky shard jobs, merge-reports failures, or an explicit 'tune CI' request.

Testing & QA

AI Index

423

mizchi/skills

Method and tooling for measuring how AI-generated a piece of prose reads, in Japanese or English. Two layers — a deterministic lint for removable surface tells (scripts/slopscore.py, no API) and a judgment layer of typed probabilistic questions (Jev noul/score) for the tells that survive editing. Includes measured human/AI baselines, a gap-first calibration procedure, and labeled fixtures. Use when building or calibrating an AI-likeness score, or when a draft needs a defensible number rather than a vibe. For writing guidance use natural-writing-ja / natural-writing-en instead.

AI, LLMs & Agents

Apm Usage

423

mizchi/skills

Reference for APM manifests, installation, targeted updates, deployment paths and lockfiles. Invoke when the user explicitly asks about APM or apm.yml, or an unfamiliar APM command/error needs exact CLI details. Do not automatically invoke for every project that happens to have installed skills.

DevOps & Cloud

Gleam Practice

423

mizchi/skills

Use when writing or reviewing Gleam code on the Erlang target — especially Wisp + Mist HTTP services, OTP-based processes (gen_server / supervisor analogues), justfile workflows, gleeunit testing, `gleam format`, GitHub Actions CI, and performance measurement. Trigger on `gleam.toml`, `.gleam` files, or Erlang/BEAM-related symptoms even if the user does not say "Gleam" by name.

Testing & QA

Flaker Storage Cache on CI

423

mizchi/skills

Persist flaker's DuckDB storage across GitHub Actions runs and feed it from multiple sources (vitest reports, custom adapter reports, etc.). Use when wiring `@mizchi/flaker` into a new repo's CI, adding a new ingest source to an existing flaker setup, or debugging why `flaker apply` / `flaker run --gate ...` "lost its history" between runs. Encodes the cache key shape, fetch-depth requirements, `--changed` derivation, and the import-step placement that internal flaker users converged on.

Testing & QA

Playwright CLI

423

mizchi/skills

Use when running Playwright via terminal CLI — `npx playwright test` (test runner), `codegen` (interactive recording), `screenshot` / `pdf` (one-off captures), and CI sharding. NOT for agent-driven real-time browser control (use `claude-in-chrome` MCP tools for that).

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.