spine-recall

Load feature-level knowledge from a Spine vault into current context.

21|2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Nodewarrior/spine --skill spine-recall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spine-recall
Source: https://github.com/Nodewarrior/spine/tree/main/skills/spine-recall
Command: npx skills add https://github.com/Nodewarrior/spine --skill spine-recall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill pulls the right Spine vault documents into context so you do not have to search through feature notes, fixes, decisions, and architecture docs manually.

Core Features & Use Cases

  • Loads every markdown document for a chosen feature area, starting with the spine note and then following linked child docs.
  • Supports targeted recall by feature name, spine note name, or keyword, plus browse mode for exploring documented features in a repository.
  • Resolves the vault path from environment settings or local config, detects the current repository, and handles missing vaults or untracked repos with clear guidance.

Quick Start

Ask the assistant to run spine-recall for the feature or topic you want loaded into context.

Frequently Asked Questions about spine-recall

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I load Obsidian vault knowledge into my current context?

To load Obsidian vault knowledge, the Skill resolves your vault path from environment or config, detects the current repo, and pulls the relevant markdown docs into context. It follows wikilinks from the spine note to load all linked child documents for the feature area.

What is the best way to pull feature notes and architecture docs from a Spine vault?

Pulling feature notes from a Spine vault is handled by resolving the vault path, detecting the current repository, and loading the spine note along with linked markdown docs. It returns a structured output contract containing the status and all loaded files.

Can I explore documented features in a repository without knowing the exact note name?

Exploring documented features is supported through browse mode. You can explore tracked repository features without a specific name, or use targeted recall to deep-load context by feature name, spine note, or keyword.

Do I need environment variables configured to use Spine vault navigation?

Spine vault navigation resolves the vault path from environment settings or local config. If the vault is missing or the repository is untracked, the Skill provides clear guidance on resolving the configuration issue.

What happens when spine-recall encounters an untracked repository or missing vault?

When encountering an untracked repository or missing vault, spine-recall handles the exception by providing clear guidance. It detects the current repo and checks the resolved vault path to ensure missing contexts are communicated effectively.

Why does context loading fail when my repository is not tracked?

Context loading fails for untracked repos because the Skill relies on detecting the current repository to locate the correct spine notes. It handles this by returning a structured output contract with clear guidance instead of proceeding with missing data.