Plugin publish

Skill racecraft-lab/racecraft-plugins-public/.claude/skills/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".From its SKILL.md

Install

npx -y skills add racecraft-lab/racecraft-plugins-public --skill plugin-publish

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.2 KB, as published. Nobody here has run it

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