cpv-batch-caching-optimize

cpv-batch-caching-optimize

Overview

Parallel cache-fix skill. Runs Phase 1 (Audit) → Phase 2 (Fix) → Phase 3 (Re-validate) of the cpv-cache-optimizer-agent workflow across every plugin in the user's input spec. Phase 4 (Broader refactor) is deliberately skipped in batch mode because every Phase 4 step requires interactive per-step approval and that doesn't compose with a parallel dispatch.

Same input grammar and dispatch shape as cpv-batch-validate. The orchestrator body lives in this plugin's commands/cpv-batch-caching-optimize.md slash-command file.

Prerequisites

• claude-plugins-validation plugin installed (provides the cpv-cache-optimizer-agent, the universal input resolver, and the cache validator + fix recipes).
• For URL inputs: git on PATH and network access to github.com.
• Write access to every plugin's tree — this skill mutates source files in place (it's the fix variant of cpv-batch-caching-audit).
• Each plugin's tree should be a clean working tree (committed or stashed) before the run so the per-plugin agents can produce inspectable fix(cache-CA-NN): ... commits.

Inputs

See the cpv-batch-validate input table — every shape is supported identically.

Instructions

1. Confirm the user wants to APPLY fixes (this skill mutates plugin files). If they want a read-only snapshot, route to cpv-batch-caching-audit.
2. Invoke the slash command body:

   /cpv-batch-caching-optimize <user's spec> [--max-parallel N]
   

3. Each agent runs Phase 1 → Phase 2 → Phase 3 on its assigned plugin (Phase 4 skipped in batch).
4. The user gets the final status table + a one-line summary (DONE: plugins=N clean=X fixed=Y partial=Z failed=W).
5. For Phase 4 (broader refactor — extracting shared cache headers, restructuring agent contexts), run the cpv-cache-optimizer-agent on that single plugin interactively (it performs Phase 4 with the required per-step approval that does not compose with a parallel batch).