Frontend Review CI
Use when CI is slow (>10 min), flaky, or the user asks to optimize GitHub Actions for a frontend project. Analyzes `gh run list` history, identifies bottleneck steps, proposes sharding / cache / concurrency improvements. Runs `scripts/audit-ci.sh`.
Install
npx skills add mizchi/skills --skill frontend-review-cigit clone --depth 1 https://github.com/mizchi/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/frontend-review-ci ~/.claude/skills/frontend-review-ciPersonal 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 — CI Optimization
You are optimizing GitHub Actions CI for a frontend project. The target is **median ≤ 10 minutes, max ≤ 15 minutes**. Faster CI means developers trust it; trust is what makes the ratchet work.
## 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.
1. Run `<skill-dir>/scripts/audit-ci.sh --repo <client-repo> --run-checks`.
2. Read `<client-repo>/.frontend-review/report/latest/raw/ci.json`.
3. For the slowest runs, dig into step-level timing:
```bash
gh run view <run-id> --log | grep -E '^\d{4}-' | head -200
```
4. Inventory current workflows under `.github/workflows/` and note:
- Does **every job** (lint, build, test, coverage, etc.) use a pnpm/npm store cache? A common miss: `test.yml` has cache but `lint.yml` and `pages.yml` do not.
- Does `actions/setup-node` use `cache: pnpm`, or is there a manual `actions/cache` block for the pnpm store? Either is fine; the key must include `hashFiles('**/pnpm-lock.yaml')`.
- Does `actions/cache` cache the Playwright browser store (`~/.cache/ms-playwright`)?
- Is there a `concurrency:` block?
- Are vitest / playwright sharded?
- Are jobs serialized via `needs:` unnecessarily?
- Are `lint` and `typecheck` in the same serial job? They have no dependency on each other and should be separate parallel jobs.
## OutputDetails
- Skill name
frontend-review-ci- Repository
- mizchi/skills
- Path
frontend-review-ci/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Frontend Review CI skill do?
Use when CI is slow (>10 min), flaky, or the user asks to optimize GitHub Actions for a frontend project. Analyzes `gh run list` history, identifies bottleneck steps, proposes sharding / cache / concurrency improvements. Runs `scripts/audit-ci.sh`.
How do I install the Frontend Review CI skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add mizchi/skills --skill frontend-review-ci. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Frontend Review CI popular?
It lives in mizchi/skills, which has 423 GitHub stars and 6 forks.
Related skills
Actions CI Tuning
423mizchi/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.
AI Index
423mizchi/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.
Apm Usage
423mizchi/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.
Frontend Review Deps
423mizchi/skills
Use when auditing dependency health — outdated packages, CVE triage with attack-vector weighting, deprecated/declining library detection (trend-watch). Runs `audit-deps.sh` and `audit-trend-watch.sh`. Pairs with `frontend-review-security` for the full security picture.
Frontend Ops Expert
423mizchi/skills
Frontend Ops specialist perspective for the weekly review. Focuses on CI/CD, Scheduler, KPI ratchet, release process, Renovate / Dependabot health.
Frontend Review Hygiene
423mizchi/skills
Use when assessing code quality hygiene — TypeScript strictness, lint violations, dead code, and duplication. Runs `audit-typescript.sh`, `audit-lint.sh`, `audit-similarity.sh`. Does NOT cover dependency freshness or CVE audit — use `frontend-review-deps` for that.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.