frontend-review-hygiene

Run deterministic audit scripts for TypeScript strictness, lint violations, dead code, and duplication.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Assess frontend projects by measuring TypeScript strictness, lint quality, dead code, and duplication to improve maintainability and reliability.

Core Features & Use Cases

  • Run automated audits for TypeScript strictness, lint violations, and code similarity to detect duplication.
  • Generate KPI reports and baseline.json to track improvements over time.
  • Use during baseline setup and weekly hygiene checks to surface actionable improvements.

Quick Start

Run the skill against a client repository to produce a hygiene KPI report and update the baseline as needed.

Frequently Asked Questions about frontend-review-hygiene

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

FAQPage Schema
How do I audit TypeScript strictness and lint violations in a frontend project?

You can audit TypeScript strictness and lint violations by running deterministic audit scripts that measure code quality issues, generating a KPI JSON report alongside a baseline file for tracking improvements over time.

What's the best way to track dead code and duplication in a frontend codebase?

Tracking dead code and duplication is done by running automated audit scripts that detect code similarity, producing quantified KPI reports and a baseline.json file to monitor frontend hygiene improvements across weekly checks.

Can I use frontend hygiene audits for pre-merge checks in CI?

Yes, frontend hygiene audits are applicable to CI setups and can be used for pre-merge checks to surface actionable code quality improvements before changes are merged.

How do I create a baseline for frontend code quality metrics?

Creating a baseline for frontend code quality involves running audit scripts against your repository to produce a baseline.json file, capturing TypeScript strictness, lint violations, dead code, and duplication metrics for future comparison.

What metrics does a frontend code quality audit report include?

A frontend code quality audit report includes KPI metrics for TypeScript strictness, lint violations, dead code, and code duplication, outputting a structured KPI JSON file for tracking maintainability and reliability.

Do I need any dependencies to run frontend hygiene audits?

No external dependencies are required to run frontend hygiene audits, as the Skill operates standalone using deterministic audit scripts to evaluate TypeScript, lint, dead code, and duplication in projects of any size.