frontend-review-triage

Generate a repository-level frontend triage scorecard from project signals.

320|3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/mizchi/skills --skill frontend-review-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-review-triage
Source: https://github.com/mizchi/skills/tree/main/frontend/review-triage
Command: npx skills add https://github.com/mizchi/skills --skill frontend-review-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The triage skill accelerates Day 0 frontend assessments by generating a structured scorecard from core project signals (package.json, README, GitHub issues, and CI/workflows), enabling quick risk awareness without proposing fixes.

Core Features & Use Cases

  • Classifies the app context (admin / toc / saas / ecommerce, etc.) and notes regulatory or authentication considerations.
  • Executes scripts/audit-triage.sh to produce a consistent triage report from project metadata and repository signals.
  • Outputs a concise triage scorecard and a short set of open questions to guide Week 1 planning.

Quick Start

Run the audit-triage script against your target repository to generate the triage scorecard.

Frequently Asked Questions about frontend-review-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a Day 0 frontend triage assessment for a TypeScript repository?

Frontend triage generates a repository-level scorecard by reading package.json, README, gh issues, and CI workflows to provide instant risk awareness for new TypeScript projects. It classifies the app context and notes regulatory or authentication considerations without proposing fixes.

What is a frontend triage scorecard and what signals does it evaluate?

A frontend triage scorecard evaluates core project signals including package metadata, README documentation, open GitHub issues, and CI workflow configurations. It classifies app contexts like admin dashboards or SaaS apps and outputs a structured report with open questions to guide Week 1 planning.

Can I run a frontend audit on marketing sites or admin dashboards with TypeScript?

Yes, frontend triage applies to TypeScript projects including admin dashboards, SaaS apps, and marketing sites. It executes an audit script to parse repository signals and produces a consistent triage report with regulatory and authentication considerations noted.

What's the best way to automate frontend dependency and CI checks for new repositories?

Running an audit-triage script automates frontend dependency and CI checks by extracting metadata from package.json and workflow files. It produces a structured scorecard that highlights risks and open questions, accelerating initial project assessments.

Does frontend triage propose fixes for risks found in package.json or CI workflows?

No, frontend triage generates risk awareness without proposing fixes. It outputs a concise scorecard and open questions based on repository signals to guide downstream Week 1 planning and analysis.

Do I need a specific CI setup to generate a frontend triage report?

Frontend triage reads existing CI and workflow configurations alongside package.json and GitHub issues to generate the scorecard. It works with standard TypeScript project structures that utilize CI pipelines for dependency checks.