Frontend Review Weekly

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.

423 stars 6 forksFrontend & Design

Install

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

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 — Weekly Orchestrator

Run the weekly evidence review, combine the domain and perspective findings, and compare measured KPIs. The review produces reports and follow-up proposals; implementation follows a separate engineering request:

1. Re-run every `frontend-review-*` skill in the correct order.
2. Run the five perspective reviews using the authorized execution mode.
3. Diff the KPIs against last week's baseline.
4. File GitHub issues for repeat findings.
5. Propose static-rule promotions for patterns that appear 3+ weeks in a row.

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

### Phase 1: raw data collection

Run, in this order. Keep partial collection reports visible and do not treat missing inputs as a passing KPI:

1. `frontend-review-triage`
2. `frontend-review-ci`
3. `frontend-review-hygiene`
4. `frontend-review-deps`
5. `frontend-review-testing`
6. `frontend-review-security`

Each of these writes to `<client-repo>/.frontend-review/report/latest/`.

### Phase 1.5: architecture review (run when findings are suspected)

Run these on-demand, or always for the first weekly of a new engagement:

7. `frontend-review-state`
8. `frontend-review-performance`

These write to `<client-repo>/.frontend-review/report/latest/md/`.

### Phase 2: perspective review (parallel)
Read the full skill on GitHub

Details

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

FAQ

What does the Frontend Review Weekly skill do?

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.

How do I install the Frontend Review Weekly skill?

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

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

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

Frontend Review Triage

423

mizchi/skills

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 & Design

Storefront Best Practices

237

medusajs/medusa-agent-skills

ALWAYS use this skill when working on ecommerce storefronts, online stores, shopping sites. Use for ANY storefront component including checkout pages, cart, payment flows, product pages, product listings, navigation, homepage, or ANY page/component in a storefront. CRITICAL for adding checkout, implementing cart, integrating Medusa backend, making a store agent-friendly for AI shopping agents, or building any ecommerce functionality. Framework-agnostic (Next.js, SvelteKit, TanStack Start, React, Vue). Provides patterns, decision frameworks, backend integration guidance.

Frontend & Design29

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