Source note
Spine – verified codebase onboarding for Claude Code
Summary
Spine is a CLI and Claude Code skill that builds a verified onboarding guide for an unfamiliar codebase. It uses static source relationships to create a small architecture map, reading order, and repo context file for later Claude sessions.
Problem
- Developers and coding agents often lose time finding entry points, subsystems, and the files to read first in a new repository.
- Existing onboarding docs can be stale, broad, or based on guesses, which can mislead humans and Claude Code sessions.
- The tool matters because repo context affects code review, bug fixing, feature work, and agent prompting.
Approach
- Spine detects likely entry points, then extracts a small “spine” from source relationships it can verify through static analysis.
- It creates a Mermaid architecture diagram only from proven edges; if Mermaid validation fails twice, the diagram is omitted.
- The
/mappath gives a deterministic map-only preview with no synthesis step and noONBOARDING.md. - The
/onboardpath writes a full guide with a verified map, reading order, mental model, subsystem summaries, gotchas, and estimated read time. - With
--write-context-file, it can refresh.claude/REPO_CONTEXT.mdso later Claude Code sessions start with a compact repo snapshot.
Results
- The excerpt reports no controlled evaluation, benchmark score, dataset result, or baseline comparison.
- A sample run detects
1JavaScript library entry point, writesONBOARDING.md, and covers7spine files and4subsystems. - The sample cost estimate is about
$0.008input plus$0.010output, or about$0.018total. - The sample claims about
3.5hours of manual exploration saved for about$0.02of LLM cost. - Current verified spine coverage lists
6language families: TypeScript/JavaScript, Python, Go, Rust, and PHP, with TypeScript and JavaScript grouped together. - The launch benchmark recommendation is
axios; follow-up demo repos named in the excerpt areglow,poetry, andlog.