/onboard-repo
Bootstrap the bassclef framework in a new repo. Installs the sync hook. Scaffolds config, whereami, and CLAUDE.md. Modes: default, --with-deploy-host, --with-secrets, --full, --greenfield-from-intent (starts a new repo from a short intent paragraph).
/onboard-repo/onboard-repo default/onboard-repo --with-deploy-host/onboard-repo --with-secrets/onboard-repo --full/onboard-repo --greenfield-from-intentType it bare, or paste it with loose context after — Claude figures out the rest.
Setting up bassclef in a new repo takes an hour of trial. Missing directories and wrong hook wiring.
One command bootstraps everything — sync hook and config file and whereami scaffold.
Takes in
- Optional flags — --with-deploy-host or --with-secrets or --full
Returns
- Installed bassclef-sync hook
- Config scaffold
- Whereami stub
What it does
Brings a repo from "zero bassclef wiring" to "inherits full substrate on desktop + mobile" in a single operator-gated session. Distinct from:
auth, service account, launchd). Run once per machine.
Read the full skill
The complete instructions live at .claude/skills/onboard-repo/SKILL.md in your repo after bassclef-sync. Open with your editor for phases, rules, and worked examples.
Where in the SDLC
Why this phase: Bootstrap bassclef framework in a new repo. First-time adoption.
Related
- Skills catalog — browse all skills grouped by lifecycle phase
- Tier system — what each tier gives you
FAQ
Terms from bassclef vocabulary that appear on this page.
- luminary
- A design or engineering thinker whose discipline bassclef borrows as a review lens — the practitioner in the cameo pattern above. Cooper for personas, Norman for signifiers, Feathers for characterization tests, Beck for TDD rhythm, plus about 90 others. Skills invoke a lens to check work against a specific discipline. `/luminary` browses the catalog. See: /docs/skills/luminary, doi:10.5281/zenodo.22145491
- temperance
- The pause-and-think gate that fires before any non-trivial work. Two questions — am I building the right thing AND am I building it the right way? Bassclef enforces it with a pre-build hook that BLOCKs edits until a temperance marker exists on the branch. See: /docs/skills/temperance
- chronicle
- A narrative log of what a session shipped — what worked, what did not, what got deferred. Written at session-end. Bassclef's chronicles live under `docs/chronicles/YYYY-MM-DD-slug.md`. Chronicles are how future sessions understand context that the code alone cannot show. See: /docs/skills/session-log
- whereami
- The authoritative project-state snapshot — current phase, active goals, subsystem status, gate progress, session recap history. Read at session-start; updated at session-end. The one file every new session should read first to know where the project stands. See: /docs/skills/whereami
- hook
- A shell script bassclef wires into Claude Code's tool-invocation lifecycle. Hooks fire at events like PreToolUse (before an Edit lands) or SessionStart (when a session opens). Hooks enforce rules mechanically — a rule says 'don't do X'; a hook fires and BLOCKs if X happens.
- rule
- A markdown file auto-loaded into every session's context. Rules pin discipline the agent applies to every response (plain-English writing, blocked-items protocol, temperance gates). Different from a hook — rules are steering; hooks are enforcement.
- skill
- A user-invocable command (like `/kiss` or `/temperance`) that runs a specific bassclef workflow. Every skill lives at `.claude/skills/<name>/SKILL.md` with frontmatter + procedure. Adopters type the slash command; Claude Code loads the skill and runs it.
- adopter
- A repo that has bassclef installed — either via `bassclef init` (lite tier from npm) or via the symlink pattern (standard tier with an Anthropic key). Bassclef's discipline: never break adopters. Every change to a downstream-observable surface ships with a compat shim.
- bassclef-upstream
- The private repo where bassclef substrate is authored. Ships to a public `bassclef` npm package + a public `bassclef-web` docs site. Adopters read the public tier; the operator maintains upstream.
Shipped by @kingofrock · Read the essays
/session-log
Write the session's log entry — what shipped, what was decided, what's still open. Reads the day's commits and conversation. Outputs a markdown entry with gates fired, sources read, and discoveries surfaced. Renamed from /chronicle.
/skill
Compose a new bassclef skill from idea to conforming SKILL.md. Runs the taxonomy gate, generates a verb-first plain-English description, scaffolds the frame, and pre-validates. Standard-tier — pending audit at bassclef-web#193.