How do I install the Plugin Publish skill?

Run npx skillmds@latest add racecraft-lab/plugin-publish in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Plugin Publish safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Plugin Publish?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Plugin Publish free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Plugin Publish?

racecraft-lab (@racecraft-lab) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Plugin Publish by racecraft-lab — Agent Skill

Name: Plugin Publish
Author: racecraft-lab

Plugin Publish

Stage, commit, push, and open a PR for plugin changes. Validates the commit message against conventional-commits (required by validate-pr-title CI check), runs Layer 1 structural tests first, and reminds the user to run /plugin marketplace update after merge. Triggers on "publish plugin", "push plugin changes", "ship this plugin", "release this branch".

racecraft-lab 1e3ce5f 2.2 KB Updated Sep 17, 2026 11 repo stars

File contents

plugin-publish

User-invocable. Stops Claude from auto-running this — it has side effects (push, PR).

What this does

Walks through the publish flow documented in CLAUDE.md, but enforces the parts that are easy to forget:

Pre-flight check — python3 tests/speckit-pro/run-all.py --layer 1 must pass (catches missing frontmatter and invalid JSON).
Detect remote — git remote -v (per global CLAUDE.md "Git Operations" rule — don't assume origin).
Stage selectively — list candidate files, ask user which to include. NEVER git add -A or git add ..
Commit with conventional-commits prefix — required types: feat, fix, chore, docs, refactor, test. Validate before writing.
Push and open PR — gh pr create with the same prefix in the title (the validate-pr-title CI check enforces this).
Remind user — after PR is merged (squash-only), tell them to run:
```
/plugin marketplace update racecraft-plugins-public
```

When NOT to use

For a release (release-please handles version bumps automatically — do not manually edit plugin.json versions)
For docs-only PRs touching CLAUDE.md or README.md (the detect CI job skips test matrix anyway; just commit + push, no skill needed)
For the marketplace.json/release-please-config.json triplet — those have their own PreToolUse guard hook

Hard rules

Never merge the PR (only humans merge — see global memory)
Never use --no-verify to skip hooks
Never push to main directly (branch protection blocks it; use a feature branch + PR)
Conventional-commit title format: <type>(<scope>): <description> (scope optional)

Output

When complete, report:

Branch name pushed
PR URL
The marketplace-update command the user needs to run post-merge

---name: plugin-publishdescription: Stage, commit, push, and open a PR for plugin changes. Validates the commit message against conventional-commits (required by validate-pr-title CI check), runs Layer 1 structural tests first, and reminds the user to run /plugin marketplace update after merge. Triggers on "publish plugin", "push plugin changes", "ship this plugin", "release this branch".license: MIT---# plugin-publishUser-invocable. Stops Claude from auto-running this — it has side effects (push, PR).## What this doesWalks through the publish flow documented in `CLAUDE.md`, but enforces the parts that are easy to forget:1. **Pre-flight check** — `python3 tests/speckit-pro/run-all.py --layer 1` must pass (catches missing frontmatter and invalid JSON).2. **Detect remote** — `git remote -v` (per global CLAUDE.md "Git Operations" rule — don't assume `origin`).3. **Stage selectively** — list candidate files, ask user which to include. NEVER `git add -A` or `git add .`.4. **Commit with conventional-commits prefix** — required types: `feat`, `fix`, `chore`, `docs`, `refactor`, `test`. Validate before writing.5. **Push and open PR** — `gh pr create` with the same prefix in the title (the `validate-pr-title` CI check enforces this).6. **Remind user** — after PR is merged (squash-only), tell them to run: ``` /plugin marketplace update racecraft-plugins-public ```## When NOT to use- For a release (release-please handles version bumps automatically — do not manually edit `plugin.json` versions)- For docs-only PRs touching `CLAUDE.md` or `README.md` (the `detect` CI job skips test matrix anyway; just commit + push, no skill needed)- For the marketplace.json/release-please-config.json triplet — those have their own PreToolUse guard hook## Hard rules- Never merge the PR (only humans merge — see global memory)- Never use `--no-verify` to skip hooks- Never push to `main` directly (branch protection blocks it; use a feature branch + PR)- Conventional-commit title format: `<type>(<scope>): <description>` (scope optional)## OutputWhen complete, report:- Branch name pushed- PR URL- The marketplace-update command the user needs to run post-merge

Frequently asked questions