cam-fleet-ops

Add Dependabot config to one or many repos. Auto-detects the lockfile ecosystem (npm/pnpm/yarn/bun/composer/pip).

Archive repos that haven't been pushed in N days. Reversible — repos can be unarchived.

One-repo lint cleanup. Reads the lint config, finds the top error rules, disables the noisy ones, commits, and verifies the next CI run is green.

Run a full fleet-wide CI/lint health audit and produce a categorized report.

Quick check for the GitHub Pro "spending limit needs to be increased" pattern across the fleet. Returns just the repos affected and the run IDs.

Diagnose and apply branch protection rules across a fleet. The standard pattern: require PR review, dismiss stale reviews, restrict who can push. Common issue: "Bypassed rule violations for refs/heads/main" — this happens when direct push is used despite protection. Use when CI builds keep failing on push branches that the user didn't intend to push to directly.

Add Dependabot config to a fleet of repos, triage auto-PRs that fail CI, and manage the auto-PR lifecycle. Covers: auto-detecting lockfile ecosystem (npm/pnpm/yarn/bun/composer/pip), writing `.github/dependabot.yml` per-repo, understanding why Dependabot PRs often fail CI (peer-dep conflicts, major version bumps), and the "billing cap vs Dependabot PR" classification trick. From a real 35-repo Dependabot rollout.

Upgrade a single repo from ESLint 8 + legacy `.eslintrc.*` config to ESLint 9 + flat config (`eslint.config.js` / `.mjs`). Handles all the v9 breaking changes: dropped `.flat` namespace in plugins, `@eslint/js` export shape, `eslint-config-next` incompatibility, `react/display-name` rule broken in v7.x. Cites real fixes from a 3-repo migration (fleetflow-mvp, family-planner, Shift6).

Audit all repos in the user's GitHub fleet for CI Build and Lint workflow health. Categorizes failures into billing-cap (spending limit), dependabot-PR, cancelled-superseded, and real-source-error buckets. Use as the first step in any "fix all known issues" task — it gives a precise inventory of what's actually broken vs what's just noise. Filters by default-branch and push/schedule events to ignore PR branches.

When a fleet-wide change breaks many repos at once, roll back across all affected repos in one sweep. The pattern: identify the breaking change, find every commit that introduced it, force-revert, push. Use after a bad fleet-wide migration (e.g., Prisma 7 broke something unexpected) or a config that was applied fleet-wide.