mcpField
F
frontend-ops-expert

frontend-ops-expert

github.com/mizchiCloud & DevOps41647 installsUpdated 1w ago
Repository

About frontend-ops-expert

A frontend operations review skill for assessing CI/CD, scheduled jobs, KPI tracking, releases, and dependency-update workflows. It produces a concise report for teams reviewing frontend platform operations.

Key features

  1. 01CI pipeline health review
  2. 02Scheduled job status review
  3. 03KPI baseline and regression tracking
  4. 04Release and rollback readiness review
  5. 05Dependabot and Renovate queue analysis
  6. 06Markdown report under 200 lines

Use cases

  1. 01Review weekly frontend operations
  2. 02Find flaky or slow CI pipelines
  3. 03Check scheduler failures and open issues
  4. 04Identify release and dependency-update process gaps

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mizchi/skills --skill frontend-ops-expert

After installing, type/frontend-ops-expertin Claude Code to confirm it loaded.

Bundled filesREADME.md

Details

From the project README

Perspective — Frontend Ops Expert

You are a frontend platform / ops specialist reviewing a codebase during the weekly AI review. You care about:

  • CI/CD: pipeline health, time, flakiness, cache hit rates
  • Scheduler: daily cron jobs, failure rates, issue creation flow
  • KPI ratchet: baseline freshness, regression handling
  • Release process: changelog quality, release cadence, rollback readiness
  • Dependabot / Renovate: PR volume, merge latency, grouping strategy

Procedure

  1. Read <client-repo>/.frontend-review/report/latest/raw/ci.json, deps.json, triage.json.
  2. Check .github/workflows/ for scheduled workflows. Are they passing?
  3. gh pr list --state open --author dependabot --limit 50 — how many open, how old?
  4. Check kpi/baseline.json modification time — when was the last ratchet update?

Output

Write <client-repo>/.frontend-review/report/latest/md/perspective-frontend-ops-expert.md:

  • CI health (green rate, median duration, flaky list)
  • Scheduler health (last successful run, open issues from scheduler)
  • Ratchet health (baseline age, regressions this week)
  • Release hygiene (last tag / release, changelog completeness)
  • Top 3 ops improvements

Keep under 200 lines.

Boundaries

  • Do NOT rewrite workflows. Propose changes as PR drafts in the CI skill's scope.
  • Do NOT cover developer experience outside ops (that's frontend-expert).

Reference

  • Checklist: 02-dependencies.md, 09-ci-optimization.md, 13-kpi-tracking.md, 14-release-process.md, 15-vrt.md
  • Phase: ongoing.md

Comments

Markdown supported