Frontend Review Triage

Use when starting a frontend review engagement or when the user asks for an initial assessment ("triage", "day 0", "what's the state of this repo"). Reads package.json, README, gh issues, and produces a scorecard covering lockfiles, TypeScript strictness, testing, CI, and known issues. Runs `scripts/audit-triage.sh`.

423 stars 6 forksFrontend & Design

Install

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

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 — Triage

You are performing Day 0 triage for a frontend consulting engagement. Your job is to produce a short, honest scorecard of the repository's current state, not to recommend fixes. Recommendations come later from the other `frontend-review-*` skills.

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

0. **Classify the app** before running any script.
   - Ask the user (or infer from README / package.json) which app type applies:
     `admin` / `toc` / `btob-saas` / `ec` / `fintech` / `healthcare` / `iot-ops` / `media`
   - Note any regulatory context (GDPR, PCI DSS, HIPAA, …) and authentication requirements.
   - Derive security, performance, type/lint, coverage and dependency priorities from the client's explicit requirements and deployed data paths. Record assumptions; a domain label alone does not establish regulatory compliance or a KPI target.
   - Save the result to `<client-repo>/.frontend-review/kpi/app-classification.json`.
1. Run `scripts/audit-triage.sh --repo <client-repo>` where `<client-repo>` is the absolute path to the user's repository.
2. Read the resulting JSON at `<client-repo>/.frontend-review/report/latest/raw/triage.json`.
3. Also quickly skim:
   - `package.json` — dependencies, scripts, engines
   - `README.md` — is it up-to-date, does it describe how to run things
Read the full skill on GitHub

Details

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

FAQ

What does the Frontend Review Triage skill do?

Use when starting a frontend review engagement or when the user asks for an initial assessment ("triage", "day 0", "what's the state of this repo"). Reads package.json, README, gh issues, and produces a scorecard covering lockfiles, TypeScript strictness, testing, CI, and known issues. Runs `scripts/audit-triage.sh`.

How do I install the Frontend Review Triage skill?

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

Is Frontend Review Triage 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

Frontend Review Weekly

423

mizchi/skills

Use for the weekly AI review. Orchestrates all frontend-review-* skills in order, runs five perspective reviews, in parallel when authorized or sequentially, diffs against last week's KPIs, and produces a weekly report that feeds the ratchet.

Frontend & Design

Frontend Review State

423

mizchi/skills

Use when reviewing state management architecture — classifying state types (server/URL/form/UI), checking for over-globalization, Jotai/Zustand/Redux patterns, derived state, and logout/cache invalidation. Covers checklist 23-state-management.md.

Frontend & Design

React Expert

423

mizchi/skills

React specialist perspective for the weekly review. Focuses on hooks discipline, re-rendering, Suspense / RSC, and Context design. Opinionated on React idioms.

Frontend & Design

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