spine-scan

Detect vault decay and undocumented changes in Spine-managed Obsidian knowledge bases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents Spine vault knowledge from drifting out of sync by detecting broken links, missing tags, orphan docs, stale notes, and undocumented recent work before the decay spreads.

Core Features & Use Cases

  • Session-start auditing: Runs an automatic vault scan at the beginning of a session when Tier 3 autonomous mode is enabled.
  • Low-risk auto-fixes: Repairs broken wikilinks, corrects type tags, and links orphan documents into the right spine note sections.
  • Coverage and health checks: Flags stale or obsolete docs, detects recent commit gaps, and prepares structured output for downstream capture workflows.
  • Use case: A developer returns to a repo after several commits and wants the AI to quietly clean obvious metadata issues, identify missing documentation coverage, and surface only the meaningful follow-up actions.

Quick Start

Ask the spine-scan skill to scan the current Spine vault, auto-fix safe issues, and report any stale docs, obsolete docs, or coverage gaps.

Frequently Asked Questions about spine-scan

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

FAQPage Schema
How do I detect broken wikilinks and stale documents in an Obsidian vault?

You can detect vault decay by running an automated scan that inspects git history and vault metadata to identify undocumented changes, broken wikilinks, missing tags, and orphan notes before the decay spreads.

What is vault decay in a git-backed knowledge base?

Vault decay is the gradual drift of content out of sync, characterized by broken wikilinks, missing type tags, orphan documents, stale notes, and recent commit gaps that lack proper documentation coverage.

How do I auto-fix orphan documents and missing tags in my notes?

You can auto-fix orphan documents and missing tags by applying conflict-safe updates during a vault scan, which repairs broken wikilinks, corrects type tags, and links orphan documents into the appropriate spine note sections.

Does automated vault scanning require git history access?

Yes, automated vault scanning requires git history access to detect recent commit coverage gaps and undocumented changes. It also requires Tier 3 autonomous opt-in and vault path resolution to safely execute updates.

Can I automatically repair Obsidian metadata issues at the start of a session?

Yes, you can automatically repair Obsidian metadata issues at session-start by enabling Tier 3 autonomous mode, which runs a vault scan to apply low-risk auto-fixes and prepare structured output for downstream capture workflows.