cpv-standardize-plugin

Standardize Plugin / Marketplace

Overview

Audits existing plugin or marketplace repositories against CPV standards and auto-fixes missing files, workflows, and hooks.

Profile-aware. The standardize flow first resolves the plugin's pipeline profile (scripts/cpv_pipeline_profile.py's resolve_pipeline_profile() — manifest cpv.pipeline_profile overrides; fails safe to standard), then generates/expects the PROFILE-APPROPRIATE templates. Do NOT migrate a non-standard plugin to the plain standard shape: a remote-validation plugin keeps its remote cpv-remote-validate gate (no re-vendored validators), a submodule-build plugin keeps its build-source submodule + shipped bin/ and submodule-aware publish.py, and a binary-release plugin keeps its SHA-pinned, least-privilege build/release workflow (SHA256SUMS + build matrix). The profile is a SELECTOR not a SUPPRESSOR — drift findings still fire against the profile's canon.

Prerequisites

• uv on PATH
• CPV plugin installed
• Target repository accessible on disk

Instructions

1. Audit a Plugin:

   uv run --with pyyaml python "${CLAUDE_PLUGIN_ROOT}/scripts/remote_validation.py" standardize <plugin-path> [--report report.md]
   

   Checks: 190+ validation rules, pipeline readiness, file inventory, .gitignore, README badges.

2. Fix a Plugin (generates missing files, does NOT modify existing code):

   uv run --with pyyaml python "${CLAUDE_PLUGIN_ROOT}/scripts/remote_validation.py" standardize <plugin-path> --fix [--dry-run]
   

3. After --fix, manually fix remaining issues:

   • Under --force-templates (the canon UPGRADE verb, NOT plain --fix), ALL agents are migrated to cpv-the-skills-menu: each agent's frontmatter skills: is rewritten to [cpv-the-skills-menu] (every other field preserved) and the mandatory dynamic-loading instruction is inserted into its body; a per-plugin skills/cpv-the-skills-menu/SKILL.md catalog is created if absent (reusing the scaffold generator so it is byte-identical). The migration is idempotent (re-running is a no-op) and skips + reports any agent file lacking YAML frontmatter — see the cpv-the-skills-menu-create skill for the canonical rewrite rules. Plain --fix never touches an agent.
   • Markdown-poison guardrail: after editing any .md, reword a line-start # / + / * prose continuation (markdownlint MD018/MD004 NIT blocks --strict).
   • .gitignore gaps, SKILL.md missing Nixtla sections, README badges, MINOR/NIT issues
   • Pre-push hook blocks on CRITICAL, MAJOR, MINOR, NIT — only WARNINGs pass
   • Empirical-loading-bugs MAJORs (added 2026-04-18) need manual fixes — see skills/cpv-canonical-pipeline/references/detailed-standard.md "Empirical Validation Rules":
     • agents field with folder paths → list specific .md files instead
     • hooks: "./hooks/hooks.json" → remove the field (default file auto-loads) or point at non-default path
     • MCP/LSP same server name in 2 sources → consolidate into one source per name
   • Layout C consistency findings (when both plugin.json and marketplace.json exist at the repo root):
     • plugin.json.name ≠ marketplace self-entry name → align both
     • plugin.json.version ≠ marketplace self-entry version → align (publish.py should bump both atomically)
     • Self-entry source ≠ "./" → set to "./"
   • Current pipeline standards — load cpv-fix-validation skill's pipeline-migration.md for the full conversion recipes:
     • §1 dangling script refs · §2 lint engine consolidation · §3 cross-platform Python (bash → Python, os.path → pathlib, hook commands) · §4 idempotent publish.py · §5 input sanitization (no shell=True; regex-validate every CLI flag / env-var / JSON field at the boundary)