mcpField
W
w-ship

w-ship

github.com/blockmaticDevelopment1647 installsUpdated 4w ago
Repository

About w-ship

w-ship is a repository skill for taking an implementation through commit and pull request creation or update. It defines branch setup, documentation, pre-push checks, and reporting requirements; it does not cover merging or deployment.

Key features

  1. 01Follow branch and fetch rules
  2. 02Implement work in complete slices
  3. 03Update matching documentation
  4. 04Run the full pre-push gate
  5. 05Push changes and create or update a PR

Use cases

  1. 01Taking a planned task from implementation to PR
  2. 02Preparing a new branch from the current origin/main
  3. 03Verifying changes before publishing
  4. 04Reporting a blocked gate and local progress

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/blockmatic/basilic-skills --skill w-ship

After installing, type/w-shipin Claude Code to confirm it loaded.

Bundled filesreferences/git-publish.md

Details

From the project README

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. 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.

Comments

Markdown supported