frontend-review-weekly

Orchestrate weekly frontend review skills to generate reproducible reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the weekly coordination and governance of frontend assessment by sequencing the review skills, aggregating KPI diffs, and surfacing issues for action.

Core Features & Use Cases

  • Orchestrates all frontend-review-* skills in a defined sequence.
  • Dispatches the five perspective sub-skills in parallel for faster insights.
  • Diffs KPIs against baselines and opens issues for repeat findings to drive improvements.

Quick Start

Run the weekly orchestrator to execute all frontend review skills and generate the final weekly report for the client repository.

Frequently Asked Questions about frontend-review-weekly

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

FAQPage Schema
How do I automate weekly frontend health reviews and KPI tracking?

Automate weekly frontend health reviews by orchestrating multiple review skills in a defined sequence to generate KPI diffs, track issues, and produce a reproducible weekly report. It coordinates cross-skill perspective analyses for ongoing frontend engagements.

What is the best way to coordinate multiple frontend review skills in parallel?

Coordinate frontend review skills by dispatching five perspective sub-skills in parallel for faster insights. The orchestrator sequences all frontend-review-* skills deterministically to ensure reproducible phase progression and traceable artifact generation.

How do I track frontend KPI diffs against baselines over time?

Track frontend KPI diffs by running the weekly orchestrator, which compares current metrics against established baselines and automatically opens issues for repeat findings to drive continuous improvements across the client repository.

Do I need reliable scheduling to generate reproducible weekly frontend reports?

Reliable scheduling is required to generate reproducible weekly frontend reports. The orchestration process depends on deterministic phase progression and artifact generation to produce traceable outputs and final weekly reports consistently.

Can I use this weekly frontend report orchestration for ongoing client engagements?

This weekly frontend report orchestration is designed for ongoing frontend engagements where teams need regular KPI diffs, issue tracking, and cross-skill perspective analyses to maintain code health over time.

Why does the weekly frontend review orchestrator open issues for repeat findings?

The weekly frontend review orchestrator opens issues for repeat findings to drive improvements by surfacing persistent problems. Diffs against KPI baselines identify recurring issues that require direct action from the development team.