mcpField
W
w-build

w-build

github.com/blockmatic-iceboxDevelopment1647 installsUpdated 4w ago
Repository

About w-build

w-build is a Basilic workflow skill for implementing a clear request or existing plan in a repository. It emphasizes repository conventions, focused checks, preserving unrelated changes, and documenting behavior changes.

Key features

  1. 01Reviews repository instructions and relevant docs
  2. 02Implements a complete slice using existing patterns
  3. 03Runs the smallest relevant check
  4. 04Investigates check failures
  5. 05Updates documentation when behavior changes

Use cases

  1. 01Implementing a planned repository change
  2. 02Adding a regression check for a logic defect
  3. 03Updating docs after behavior or command changes

Install

Copy the command and run it in a terminal.

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

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

Details

From the project README

Use an existing plan or a sufficiently clear implementation request. Read repository instructions, affected README/scripts, matching rules and skills, and technical docs. Resolve consequential decisions from matching docs; ask a human for product scope, secrets, or destructive operations. Do not commit.

  1. Inspect the working tree and identify the files owned by this task. State the acceptance conditions; preserve unrelated changes. If there is no plan and the area spans packages or is unfamiliar, follow council steps 1–3 first.
  2. Implement one complete slice using existing packages and patterns. Change owning schemas and run documented generators instead of editing generated clients or migrations.
  3. Run the smallest existing check for this change. A reproducible logic defect should have a regression check; use TDD when requested or required by the repository, not as a ritual for prose edits. Never the full pre-push suite (/w-ship owns that).
  4. Investigate failed checks before building dependent work. Separate regressions caused here from pre-existing or environmental failures; never weaken checks to obtain a pass.
  5. If behavior, commands, or conventions changed, update matching MDX and nearest README; otherwise one line why not.

Comments

Markdown supported