Agent skill

Frontend Review Testing

by mizchi in mizchi/skills

A skill your agent uses when auditing test infrastructure — vitest coverage, playwright configuration, VRT setup, coverage merging.

No licenceAuto-check passedTesting & QA

Install Frontend Review Testing

skills CLI
$ npx skills add mizchi/skills --skill frontend-review-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mizchi/skills frontend-review-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mizchi/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/frontend-review-testing .claude/skills/frontend-review-testing && rm -rf skills-src

Use ~/.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/

Facts

Skill name
frontend-review-testing
GitHub stars
359
Token cost
~1.4k tokens
SKILL.md length
590 words
Files
2
Skills in repo
69
Repo updated
First seen
Licence
None found

At a glance

A skill your agent uses when auditing test infrastructure — vitest coverage, playwright configuration, VRT setup, coverage merging.

  • Works in 3 steps: Run scripts/audit-coverage.sh --repo . → Read coverage/coverage-summary.json if… → Inspect
  • Auditing test infrastructure — vitest coverage
  • SKILL.md covers Procedure, Output, Component Testing — Testing… and In-Source Testing Pattern, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Frontend Review Testing is an agent skill from mizchi/skills. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).

It sits in Testing & QA, covering Unit testing and Browser testing. It works with Vitest, Playwright and Testing Library. The repository describes itself as: Agent skills by mizchi, distributed via APM.

When your agent uses it

  • Auditing test infrastructure — vitest coverage
  • Playwright configuration
  • Coverage merging

Example prompts

  • “/frontend-review-testing”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Run scripts/audit-coverage.sh --repo .
  2. Read coverage/coverage-summary.json if it exists.
  3. Inspect

What it can do on your machine

Read from SKILL.md and the folder at commit 62f5808. 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 (its code samples are typescript).

    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

Frontend Review Testing loads about 1.4k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 590 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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

Without a licence we can't republish the file, so here is its outline and opening line. It has 590 words (~1,364 tokens).

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

— opening of SKILL.md by mizchi
name
frontend-review-testing

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file in frontend-review-testing of mizchi/skills.

  • SKILL.md
  • README.md

Open the folder on GitHubat commit 62f5808

Compare with similar skills

Frontend Review Testing 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.

Frontend Review Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Frontend Review Testing this skillmizchi/skills359—~1.4kAutomated safety check: PassNone
Playwright Testingchongdashu/vibejam-starter-pack149—~2.1kAutomated safety check: PassNone
React Testingaffaan-m/ECC276k1 repos~3.3kAutomated safety check: PassMIT
Frontend Typescript Testingshinpr/ai-coding-project-boilerplate233—~1.5kAutomated safety check: PassMIT
Test CommanderEliasOulkadi/shokunin114—~3kAutomated safety check: NotesMIT
Front End Testingcitypaul/.dotfiles740—~6.2kAutomated safety check: PassCustom licence

Similar skills

  • Playwright Testing

    chongdashu/vibejam-starter-pack

    Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.

    149 GitHub stars~2.1k tokensUpdated 5 mo ago
    Testing & QAAuto-check passed
  • React Testing

    affaan-m/ECC

    React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress…

    276k GitHub starsUsed in 1 repo~3.3k tokens
    Testing & QAAuto-check passed
  • Frontend Typescript Testing

    shinpr/ai-coding-project-boilerplate

    Designs frontend tests using the repository's configured React test and browser harnesses, including RTL, MSW, Vitest, and Playwright when present.

    233 GitHub stars~1.5k tokensUpdated 6 days ago
    Testing & QAAuto-check passed
  • Test Commander

    EliasOulkadi/shokunin

    Generate unit, integration, E2E, and visual regression tests following the Testing Trophy methodology (80% integration).

    114 GitHub stars~3k tokensUpdated 5 days ago
    Testing & QAAuto-check: notes
  • Front End Testing

    citypaul/.dotfiles

    Behavior-driven UI testing patterns across Vitest Browser Mode, Playwright E2E evidence boundaries, and DOM Testing Library.

    740 GitHub stars~6.2k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Frontend Typescript Testing

    shinpr/ai-coding-project-boilerplate

    リポジトリで設定済みのReactテスト・ブラウザハーネスを使用してフロントエンドテストを設計。RTL、MSW、Vitest、Playwrightが存在する場合に適用。コンポーネント、loading/error state、統合、フロントエンドE2Eテストの追加・レビュー時に使用。

    233 GitHub stars~843 tokensUpdated 6 days ago
    Testing & QAAuto-check passed

More from mizchi/skills

All 69 skills in this repo
  • Publish Agent Skill

    mizchi/skills

    Package, publish, verify and update an agent skill through a Claude Code plugin marketplace, APM or the npx skills CLI.

    359 GitHub stars~1.7k tokensUpdated 7 days ago
    Auto-check passed
  • AI Index

    mizchi/skills

    Method and tooling for measuring how AI-generated a piece of prose reads, in Japanese or English.

    359 GitHub stars~3.6k tokensUpdated 7 days ago
    Auto-check passed
  • Cloudflare Deploy

    mizchi/skills

    Deploy applications and infrastructure to Cloudflare with the cf CLI and typed cloudflare.config.ts.

    359 GitHub stars~2.9k tokensUpdated 7 days ago
    Auto-check: notes
  • Review Image

    mizchi/skills

    Review screenshots or other images with OpenRouter vision models via bundled Deno scripts.

    359 GitHub stars~1.3k tokensUpdated 7 days ago
    Auto-check passed
  • Post-generation safety checks for sqlc-gen-moonbit + Cloudflare D1.

    359 GitHub stars~995 tokensUpdated 7 days ago
    Auto-check passed
  • Apm Usage

    mizchi/skills

    Reference for APM (Agent Package Manager) — apm.yml syntax, install / uninstall / update commands, target detection, lockfile workflow.

    359 GitHub stars~1.9k tokensUpdated 7 days ago
    Auto-check passed

Categories

Questions about Frontend Review Testing

What does Frontend Review Testing do?

A skill your agent uses when auditing test infrastructure — vitest coverage, playwright configuration, VRT setup, coverage merging. Frontend Review Testing is an agent skill from mizchi/skills. Use when auditing test infrastructure — vitest coverage, playwright configuration, VRT setup, coverage merging.

When should I use Frontend Review Testing?

Frontend Review Testing fits situations like: auditing test infrastructure — vitest coverage; playwright configuration; coverage merging.

How do I install Frontend Review Testing in Claude Code?

Run `npx skills add mizchi/skills --skill frontend-review-testing -a claude-code`. Or copy the skill folder (frontend-review-testing in mizchi/skills) into .claude/skills/frontend-review-testing in your project. Claude Code loads it when a task matches its description.

How do I install Frontend Review Testing in Codex?

Run `npx skills add mizchi/skills --skill frontend-review-testing -a codex`. Or copy the skill folder (frontend-review-testing in mizchi/skills) into .agents/skills/frontend-review-testing in your project. Codex loads it when a task matches its description.

Can I use Frontend Review Testing 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 mizchi/skills --skill frontend-review-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontend-review-testing, .gemini/skills/frontend-review-testing, .github/skills/frontend-review-testing and .opencode/skills/frontend-review-testing in your project.

What does Frontend Review Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Frontend Review Testing is instructions for the agent only.

Does Frontend Review Testing 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 Frontend Review Testing 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 Frontend Review Testing use?

No licence was found for Frontend Review Testing or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Frontend Review Testing use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 Frontend Review Testing?

Skills that share tags, products or a category with Frontend Review Testing: Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars), React Testing (affaan-m/ECC, 276k stars), Frontend Typescript Testing (shinpr/ai-coding-project-boilerplate, 233 stars) and Test Commander (EliasOulkadi/shokunin, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Frontend Review Testing?

mizchi (a GitHub user) maintains it in mizchi/skills, which has 359 GitHub stars. The repository holds 69 skills in this directory. The repository was last updated on October 2, 2026.

Source: mizchi/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.