vercel-optimize-revanced

name	Vercel Optimize Revanced
description	RUN observability-first Vercel cost and performance optimization audit. Collect Vercel metrics, usage, project config, and code scan results FIRST. Investigate only metric-backed candidates. Produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger: Vercel bill reduction, slow/expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, CWV, Bot Management, Fluid compute, cost breakdown requests. Next.js App Router, SvelteKit, Nuxt supported. Astro limited.
metadata	{"version":"1.3.0","last_updated":"2026-06-28T00:00:00.000Z"}
stacks	["Vercel","Next.js 16 (App Router)","SvelteKit","Nuxt","Astro (limited)"]
related_skills	["vercel-deploy-revanced","vercel-cli-tokens-revanced"]
category	vercel-revanced
version	1.3.0

Vercel Optimize

IDENTIFY: When to Activate

Activate when user requests:

• Vercel bill reduction or cost analysis
• Route performance optimization
• Caching recommendations
• Function Invocations, Build Minutes, or Fast Data Transfer analysis
• Core Web Vitals improvement on Vercel
• Bot Management or Fluid compute recommendations
• General "optimize my Vercel deployment"

PREREQUISITES (2026)

• Vercel CLI v53+
• Node.js 20+
• Authenticated CLI session: vercel login
• Linked app directory: vercel link
• Observability Plus, $1.20 per 1M events (no base fee as of April 2026)

DECIDE: Execution Flow

1. COLLECT metrics + scan codebase → merge into signals.json
2. CHECK for blockers (framework support, Observability Plus, scope)
   IF blocked → stop and follow blocker resolution
3. GATE candidates → determine which routes/files deserve investigation
4. INVESTIGATE candidates → deep-dive into specific files
5. VERIFY recommendations → check claims, citations, version fit
6. RENDER report → final output to user

EXECUTE: Pipeline Steps

Step 1: Collect: Scan, Merge

RUN_DIR="$(mktemp -d -t vercel-optimize-XXXXXX)"

node scripts/collect-signals.mjs [projectId] > "$RUN_DIR/vercel-signals.json" 2> "$RUN_DIR/collect.stderr"
node scripts/scan-codebase.mjs <repo-root> > "$RUN_DIR/codebase.json"
node scripts/merge-signals.mjs "$RUN_DIR/vercel-signals.json" "$RUN_DIR/codebase.json" --out "$RUN_DIR/signals.json"

COLLECTION RULES:

• Keep stdout JSON separate from stderr logs, do NOT combine streams
• Validate JSON after collection: node -e 'JSON.parse(fs.readFileSync(...))'
• Use fresh RUN_DIR per audit, never reuse across runs
• All metrics on shared 14-day window
• Resolve project scope before collecting, unscoped commands report wrong org