Frontend Review Triage logo

Frontend Review Triage

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

Overview

Publishermizchi
Repositoryskills
Skill namefrontend-review-triage
Stars
333
Forks
4
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by mizchi on GitHub. Read the source before you install it.

Installation

Install the Frontend Review Triage AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
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
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Frontend Review Triage in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Frontend Review Triage on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Frontend Review Triage is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

  1. 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.
  2. Run scripts/audit-triage.sh --repo <client-repo> where <client-repo> is the absolute path to the user's repository.
  3. Read the resulting JSON at <client-repo>/.frontend-review/report/latest/raw/triage.json.
  4. 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
  5. 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

Frequently asked questions

What does the Frontend Review Triage AI 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`.

Why use Frontend Review Triage on TypingMind?

Because you install it once and use it with any model. Frontend Review Triage is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Frontend Review Triage in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mizchi/skills/tree/main/frontend-review-triage. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Frontend Review Triage?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Frontend Review Triage?

As many as you like. As long as a model supports skills, you can use Frontend Review Triage with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Frontend Review Triage AI skill free?

It is published on GitHub by mizchi. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇