frontend-review-ci

Analyze GitHub Actions workloads to diagnose frontend CI bottlenecks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Frontend CI often slows down development cycles. This Skill helps teams speed up feedback by diagnosing and addressing CI bottlenecks in GitHub Actions.

Core Features & Use Cases

  • Analyze gh run list history to identify slow steps across lint, build, test, and coverage.
  • Inventory workflows under .github/workflows and evaluate cache usage, concurrency, and job serialization.
  • Propose sharding, caching, and concurrency improvements, and generate actionable patches and a PR description.

Quick Start

Run scripts/audit-ci.sh against the target repository to begin optimizing CI.

Frequently Asked Questions about frontend-review-ci

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

FAQPage Schema
How do I identify and fix frontend CI bottlenecks in GitHub Actions?

To resolve frontend CI bottlenecks in GitHub Actions, analyze gh run list history to identify slow steps across lint, build, test, and coverage, then apply sharding and caching improvements.

What causes slow or flaky GitHub Actions workloads in frontend projects?

Poor cache usage, strict job serialization, and lack of concurrency across multiple workflows typically cause slow or flaky GitHub Actions workloads in frontend projects.

How do I audit and reduce median CI time for a frontend repository?

Reduce median CI time by running an audit script against the target repository that diagnoses bottlenecks and reads the generated CI JSON report to propose actionable patches and a PR description.

Can I use this to inventory GitHub Actions workflows and evaluate cache usage?

Yes, you can inventory workflows under .github/workflows to evaluate cache usage, concurrency, and job serialization, directly targeting CI feedback speed improvements.

Do I need any external dependencies to optimize frontend CI with this approach?

No external dependencies are required; the optimization process executes a local audit script to analyze GitHub Actions workloads and generates a diagnostic JSON report for bottleneck identification.