claude-plugin-repo-ci-release

Adds CI validation and release-on-version-bump GitHub Actions to Claude Code plugin repos.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/wan-huiyan/claude-ecosystem-hygiene --skill claude-plugin-repo-ci-release-wan-huiyan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-plugin-repo-ci-release
Source: https://github.com/wan-huiyan/claude-ecosystem-hygiene/tree/main/plugins/claude-plugin-repo-ci-release
Command: npx skills add https://github.com/wan-huiyan/claude-ecosystem-hygiene --skill claude-plugin-repo-ci-release-wan-huiyan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve? Claude Code plugin and marketplace repos silently break when a marketplace.json typo, a mismatched plugin.json name, or an unregistered plugin folder slips through review, and their GitHub Releases drift behind the shipped version because releases are cut by hand. This Skill installs two small guards — a structural validator running on every PR and an automatic release job keyed to a VERSION file — so both failure modes are caught or eliminated. ## Core Features & Use Cases - Structural validation CI: Bundles a stdlib-only Python validator that checks marketplace.json integrity, plugin registration, plugin.json name/dir agreement, SKILL.md frontmatter names, and VERSION drift, wired into a GitHub Actions workflow on every PR and push. - Release-on-version-bump: A release workflow that cuts a GitHub Release with generated notes whenever the repo-root VERSION file changes on the default branch, and cleanly no-ops if the release already exists. - Dual layout support: Handles both multi-plugin marketplace bundles (flat plugins/<name>/) and single multi-skill plugins (nested plugins/<name>/skills/<skill>/), auto-detected by the validator. - Use Case: A plugin repo shipped skill v3.3.0 but its GitHub Release still says v2.0.0. Use this Skill to add the validator and release workflow via a PR, so future version bumps automatically cut matching releases. ## Quick Start Set up CI validation and automatic release-on-version-bump for my Claude Code plugin repo using the bundled validator script and workflow templates.

Frequently Asked Questions about claude-plugin-repo-ci-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up CI for a Claude Code plugin repo?

Copy the bundled validate_plugins.py script to .github/scripts/ and the ci.yml template to .github/workflows/, then open a PR. The validator runs on every PR and push, checking marketplace.json, plugin registration, and SKILL.md frontmatter names.

How to automatically create GitHub Releases on version bump?

Add a repo-root VERSION file and the release.yml workflow, which triggers when VERSION changes on the default branch. It reads the version, checks whether the release exists, and cuts a GitHub Release with generated notes if missing.

Does the validator support multi-plugin marketplace repos?

Yes, the validator auto-detects both layouts: multi-plugin bundles with flat plugins/<name>/ directories and single multi-skill plugins with nested plugins/<name>/skills/<skill>/ structures. No configuration is needed to switch between them.

Why does pushing GitHub Actions workflow files fail?

Pushing files under .github/workflows/ requires the gh token to have the workflow scope. Check with gh auth status, and if the scope is missing, run gh auth refresh -s workflow before pushing.

When should I not use this CI and release setup?

Do not use it for generic app CI like pytest or lint pipelines, container deploy workflows, npm semantic-release or cargo tooling, authoring a marketplace.json from scratch, or one-off manual releases. It targets only Claude Code plugin and marketplace repo structure validation and release automation.