docs: make 'bootstrap first' explicit in GETTING_STARTED#2
Merged
Conversation
On a freshly generated repo there's no build system yet, so real gate commands fail rather than skip. Add a note to Step 3: either scaffold a minimal buildable skeleton before wiring real gates, or keep gates empty until a bootstrap task lands — and never point a gate at a command that can't pass (a red test_affected blocks the Stop hook and every 'done'). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Problem
GETTING_STARTED.mdStep 3 tells you to sanity-checkgate.sh build|lint|test, but on a freshly generated repo there's no build system yet — so real gate commands fail rather than skip (pnpm -r buildwith no workspace,forge testwith nofoundry.toml, etc.). The first pilot run then can't go green, and a redtest_affectedblocks theStophook.Hit this directly when adapting the template to a new project — had to scaffold a buildable skeleton before the gates and the pilot would work.
Fix
Add a short "Bootstrap first" callout to Step 3 with two acceptable paths:
""= skipped) until an explicit "bootstrap the workspace" ticket lands.Plus the rule of thumb: never point a gate at a command that can't pass yet.
Docs-only change.
🤖 Generated with Claude Code