w-ship — Claude Code skill: what it does and how to install
The w-ship Claude Code skill takes a requested change from implementation through pull request. It reads repository guidance, validates the work, commits it, and creates or updates a PR.
MIT 647 installs ★ 1 updated 2026-10-02
npx skills add blockmatic-icebox/basilic-skills --skill w-ship -a claude-codeWhat w-ship does
w-ship implements a requested change, checks it, and publishes it through a pull request. It reads the task or plan, repository instructions, branch state, affected docs, and scripts. The workflow follows the repository's Git publishing rules and covers the full path to a PR, rather than stopping at a commit or moving on to a merge or deployment.
Changes are made in complete slices. When behavior or commands change, the skill updates the matching MDX and nearest README. It runs the repository's full pre-push gate: pnpm qa in Basilic, or the documented equivalent in another repository. A dirty working tree stops the workflow; it does not stash changes. After validation, w-ship commits task-owned changes, pushes to the inspected upstream, and creates or updates the PR. If a gate fails, it reports the blocker and local work completed instead of presenting an unpublished change as shipped.
What it helps with
- carry a requested change through to a pull request
- run the repository's pre-push checks before publishing
- update docs when behavior or commands change
- create or update a PR after pushing a branch
Example prompts for the agent
- Implement this change, run the checks, and open a pull request.
- Take this plan through to a PR and report the check results.
- Make the requested change and update the related README if commands change.
How to install w-ship
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-ship -a claude-code2Manually: put the files in place
~/.claude/skills/w-ship/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/w-ship/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-ship -a codex2Manually: put the files in place
.agents/skills/w-ship/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-ship -a cursor2Manually: put the files in place
.cursor/skills/w-ship/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install blockmatic-icebox/basilic-skills skills/workflow/w-ship2Manually: put the files in place
.github/skills/w-ship/SKILL.md1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-ship -a gemini-cli2Platform CLI
gemini skills install https://github.com/blockmatic-icebox/basilic-skills --path skills/workflow/w-shipManually: put the files in place
.devin/skills/w-ship/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-ship -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about w-ship
How do I install w-ship in Claude Code?
Run npx skills add blockmatic-icebox/basilic-skills --skill w-ship -a claude-code. The skill file is at ~/.claude/skills/w-ship/SKILL.md.
What does w-ship do?
It implements a change, runs the full pre-push gate, commits and pushes the work, then creates or updates a PR. It reports the commit, branch, PR link, and checks.
What happens if the working tree is dirty?
The workflow stops and does not stash the changes. If a validation gate fails, w-ship reports the blocker and the local work completed.
Source text
SKILL.md · MIT
--- name: w-ship description: Implement the requested change, validate, commit, push, and create its PR. disable-model-invocation: true --- Invocation requests the complete implementation-to-PR path, not a lone commit (`/w-commit`) and not merge or deploy. Read the task or plan, repository instructions, branch state, affected docs, and scripts. Follow [git publish](references/git-publish.md). Do not open a child SKILL.md unless that Git step is blocked. 1. Follow git-publish branch rules. Dirty tree stops (no stash). Every new branch: `git fetch origin` then `git switch -c <name> --no-track origin/main` — never skip fetch, never a stale local `main`. 2. Implement in complete slices. Docs as `/w-build`: matching MDX and nearest README when behavior/commands/conventions changed, or one line why not. 3. Run the repository's full pre-push gate (`pnpm qa` in Basilic, or the consuming repo's documented equivalent). This is the only playbook that requires that gate. Diagnose failures before publishing. 4. Commit task-owned changes, then push the inspected upstream. 5. Create or update the PR. Return commit, branch, PR link, and checks. If a gate fails, report the blocker and completed local work; do not present an unpublished change as shipped.
© blockmatic-icebox · MIT · blockmatic-icebox/basilic-skills