spine-update

Update existing Spine documentation by appending new context without overwriting prior content.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It keeps Spine documentation current after a work session by adding new context to existing docs instead of creating conflicting duplicates or overwriting history.

Core Features & Use Cases

  • Targeted updates: Refresh a specific spine note or doc when you already know the feature, file, or note name.
  • Auto-detection: Find stale docs by checking recent git commits against the files each doc references.
  • Safe enrichment: Append timestamped update sections, merge wikilinks into See Also, and record the change in the curator log.
  • Use case: After shipping a bug fix, use this Skill to fold the latest decisions, trade-offs, and changed files into the existing Obsidian knowledge base.

Quick Start

Ask the spine-update skill to update the relevant Spine doc for your current repo session and append the latest context without removing any prior content.

Frequently Asked Questions about spine-update

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

FAQPage Schema
How do I update Obsidian documentation after a work session without overwriting prior content?

To update Obsidian documentation safely, append timestamped update sections and merge new wikilinks into existing notes. This approach preserves historical context while folding in the latest decisions and changed files from your recent work.

How do I find stale documentation notes in a git-backed Obsidian vault?

You can find stale notes by analyzing recent git commits against the files each documentation note references. This auto-detection identifies docs impacted by recent code changes and flags them for a targeted refresh.

Can I refresh a specific Obsidian note instead of updating the entire vault?

Yes, you can perform a targeted update on a specific note when you already know the feature, file, or note name. This refreshes only the relevant documentation without scanning the entire repository history.

Does updating Obsidian wikilinks automatically merge new connections into existing notes?

Yes, updating wikilinks merges new connections into the See Also sections of existing notes. This ensures cross-references remain intact and avoids creating conflicting duplicates during the documentation enrichment process.

How do I log documentation changes when maintaining an Obsidian knowledge base?

To log documentation changes, record each update in a curator log. This tracks appended context, resolved conflicts, and merged wikilinks, providing an audit trail of how your knowledge base evolves after each work session.

What is the best way to maintain knowledge management docs alongside active code changes?

The best way to maintain knowledge management docs is to analyze git history and append new context to existing notes. This prevents overwriting historical decisions while keeping documentation synchronized with active code changes.