About w-ship
w-ship is a Basilic workflow skill for taking an implementation from repository review through validation and a pull request. It requires the documented full pre-push gate before publishing and reports the resulting commit, branch, PR, and checks.
Key features
- 01Reviews repository instructions and branch state
- 02Implements changes in complete slices
- 03Updates relevant documentation
- 04Runs the full pre-push gate
- 05Commits, pushes, and creates or updates a PR
Use cases
- 01Taking a requested change through PR creation
- 02Preparing and validating a new branch
- 03Reporting a gate failure without claiming publication
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/w-shipin Claude Code to confirm it loaded.
Details
From the project READMEInvocation 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. Do not open a child SKILL.md unless that Git step is blocked.
- Follow git-publish branch rules. Dirty tree stops (no stash). Every new branch:
git fetch originthengit switch -c <name> --no-track origin/main— never skip fetch, never a stale localmain. - Implement in complete slices. Docs as
/w-build: matching MDX and nearest README when behavior/commands/conventions changed, or one line why not. - Run the repository's full pre-push gate (
pnpm qain Basilic, or the consuming repo's documented equivalent). This is the only playbook that requires that gate. Diagnose failures before publishing. - Commit task-owned changes, then push the inspected upstream.
- 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.
Comments
Markdown supported