ship-pluginlisted
Install: claude install-skill tonykipkemboi/skill-foundry
# Ship Plugin
Drive the full pipeline: take loose skill files (SKILL.md, .skill archives, reference
docs), package them into this plugin, run all policy checks locally, and open a PR to
the department's GitHub repo. CI is the authoritative gate, so never push to `main`.
Optimize for **accuracy over speed**: each step below guards against a known failure
mode. Do them all, in order, even when the change looks trivial.
## Two rules before you touch anything (read first)
These apply no matter which assistant runs this (Claude Code, Codex, etc.):
1. **Work on a branch, never on `main`.** Before *any* commit, run
`git rev-parse --abbrev-ref HEAD`. If it returns `main`, **create a feature branch
first** (`git checkout -b add-<skill-name>`). Do not commit, edit-then-commit, or push
on `main` at any point. Every change ships through a branch and a PR.
2. **When you need a decision, ask. Don't guess.** Whenever the next step depends on a
choice only the user can make, STOP and ask using the **AskUserQuestion** tool (or your
platform's equivalent interactive prompt) before proceeding. Examples that *require*
asking: new plugin vs. add-to-existing; the plugin name/slug; which existing plugin to
target; what the skill should be named if it's ambiguous; whether to include a skill
that won't work in the target runtime; the semver bump level if unclear. Never assume a
consequential answer.
**Make each question easy to answer well.** Use the normal terms