How do I install the Frontend Review Triage skill?

Run npx skillmds@latest add mizchi/frontend-review-triage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Frontend Review Triage safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Frontend Review Triage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Frontend Review Triage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Frontend Review Triage?

mizchi (@mizchi) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Frontend Review Triage by mizchi — Agent Skill

Name: Frontend Review Triage
Author: mizchi

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

mizchi Updated Sep 17, 2026

File contents

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

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.
- Read checklist/00-app-classification.md Step 3 to determine which security, performance, TypeScript strictness, lint, coverage targets, and dependency freshness checks are P0 vs P1 vs skip for this app type.
- Save the result to <client-repo>/.frontend-review/kpi/app-classification.json.
Run scripts/audit-triage.sh --repo <client-repo> where <client-repo> is the absolute path to the user's repository.
Read the resulting JSON at <client-repo>/.frontend-review/report/latest/raw/triage.json.
Also quickly skim:
- package.json — dependencies, scripts, engines
- README.md — is it up-to-date, does it describe how to run things
- .github/workflows/ — which workflows exist
- gh issue list --state open --limit 20 --json number,title,labels — what's already flagged
Cross-reference against checklist/12-known-issues.md for the "known issues" collection routine.

Output

Write a Markdown report to <client-repo>/.frontend-review/report/latest/md/triage-scorecard.md with:

App classification — type ID and key domain notes (1–3 lines)
Priority overrides — which P0 security/perf checks apply to this app type
Scorecard table (copy from raw/triage.json and annotate)
Top 3 risks — what would you fix first? Flag whether each risk is P0 or P1 per the classification matrix.
Open questions for the client (things you can't tell from the code)
Next phase — which checklist/ items the Week 1 plan should target, ordered by the classification priority

Keep the entire report under 400 lines. If you find yourself writing more, you're analyzing instead of triaging.

Boundaries

Do NOT propose fixes beyond a short "top 3 risks" section. Each risk is one sentence.
Do NOT run any other audit-*.sh script — leave those for the domain-specific skills.
Do NOT modify any files outside <client-repo>/.frontend-review/.
Do NOT push commits or create PRs in the client repo.

Reference

Checklist: checklist/00-app-classification.md, checklist/12-known-issues.md, checklist/01-package-manager.md, checklist/02-dependencies.md
Phase: phase/day-0-triage.md

---name: frontend-review-triagedescription: 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`.---# Frontend Review — TriageYou 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.## Procedure0. **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. - Read `checklist/00-app-classification.md` Step 3 to determine which security, performance, TypeScript strictness, lint, coverage targets, and dependency freshness checks are P0 vs P1 vs skip for this app type. - 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 - `.github/workflows/` — which workflows exist - `gh issue list --state open --limit 20 --json number,title,labels` — what's already flagged4. Cross-reference against `checklist/12-known-issues.md` for the "known issues" collection routine.## OutputWrite a Markdown report to `<client-repo>/.frontend-review/report/latest/md/triage-scorecard.md` with:- **App classification** — type ID and key domain notes (1–3 lines)- **Priority overrides** — which P0 security/perf checks apply to this app type- **Scorecard table** (copy from `raw/triage.json` and annotate)- **Top 3 risks** — what would you fix first? Flag whether each risk is P0 or P1 per the classification matrix.- **Open questions** for the client (things you can't tell from the code)- **Next phase** — which `checklist/` items the Week 1 plan should target, ordered by the classification priorityKeep the entire report under 400 lines. If you find yourself writing more, you're analyzing instead of triaging.## Boundaries- Do NOT propose fixes beyond a short "top 3 risks" section. Each risk is one sentence.- Do NOT run any other `audit-*.sh` script — leave those for the domain-specific skills.- Do NOT modify any files outside `<client-repo>/.frontend-review/`.- Do NOT push commits or create PRs in the client repo.## Reference- Checklist: `checklist/00-app-classification.md`, `checklist/12-known-issues.md`, `checklist/01-package-manager.md`, `checklist/02-dependencies.md`- Phase: `phase/day-0-triage.md`

Frequently asked questions