Repository navigation
feat!: builder has seven skills and three commands - #34
Closed
Lutherwaves wants to merge 1 commit into
Closed
Lutherwaves wants to merge 1 commit into
Lutherwaves wants to merge 1 commit into
Conversation
feat: a review that drops noise, and a build that answers review comments
Owner
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What a person can now do
A person who installs builder sees seven skills, and each one is a stage of the work or the frame around it:
builder,shape,plan,build,review,ship,security. A new session shows the soul and asks nothing.Why
Six skills were never used:
budget,canon,fleet,harness,intake,reach. Tenet 4 says: delete what nobody uses. They cost every user context and install size, and they cost the maintainer tests and evals.What goes
reach,budget,mcpmergeandledger. The binary keepshook,securityandversion.What changes in what stays
shipchecks commit signing itself, and checksghwhen the remote is on github.com. When a check fails, it stops and names the fix.tests/removed_test.gofails when a file that stays tells anyone to use a removed thing.CHANGELOG.mdlists what went. Release 3.0.0 is the last one that has it.Breaking for each person who invokes a removed skill or command.
Proven
go test ./...passes, andbash tests/test_hook.shpasses, also with a 3.0.0 ledger file present.bash scripts/validate.shprints "all checks passed" (scrub skipped: no denylist), andbash tests/test_validate.shexits 0.ls skillsprints seven folders. A fresh build printsusage: builder <hook|security|version> ....Not proven
ship,builderandflow-gatesfixtures have not been run again after this change.ghis missing and the remote is on GitHub". Theshipfixture has no remote, so it grades the signing stop only.Stack
Second of three. Base:
feat/framework. Design:docs/specs/2026-11-11-decommission-design.md.🤖 Generated with Claude Code