spine-capture

Capture completed engineering work into structured Obsidian docs with wikilinks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns completed work into structured Obsidian documentation so important fixes, features, decisions, and plans are not lost after a session ends.

Core Features & Use Cases

  • Automatically detects the repository, feature area, and document type from git context.
  • Drafts Obsidian-ready notes for fixes, features, architecture, plans, and decisions with tags and wikilinks.
  • Supports batch capture at session end, vault path resolution, spine note updates, and pattern checks for stale or missing documentation.
  • Use case: after finishing a bug fix, ask it to capture the change into the correct vault folder and update the related spine note.

Quick Start

Ask the skill to capture your completed work as a Spine doc and update the related Obsidian note.

Frequently Asked Questions about spine-capture

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

FAQPage Schema
How do I automatically capture completed git work into Obsidian documentation?

Capturing completed git work into Obsidian documentation is done by detecting the repository and feature area from git context to draft structured notes with tags and wikilinks. It supports fixes, features, architecture decisions, and plans.

What is the best way to update Obsidian spine notes after a batch coding session?

The best way to update Obsidian spine notes after a batch coding session is using the batch capture feature at session end. It resolves vault paths, classifies documents, updates wikilinks, and uses approval-aware handling for the changes.

Can I use this to organize architecture decisions and feature plans in my Obsidian vault?

You can use this to organize architecture decisions and feature plans in your Obsidian vault. The Skill drafts Obsidian-ready notes for these specific document types, applies relevant tags, and inserts wikilinks to connect related entries.

Do I need git repositories set up to generate knowledge management notes?

Git repositories must be set up to generate knowledge management notes. The Skill requires repo detection to automatically identify the feature area and classify the document type from your recent engineering work.

Why are my Obsidian wikilinks not updating when I capture a new bug fix?

If your Obsidian wikilinks are not updating when you capture a new bug fix, verify the vault path resolution and document classification. The Skill performs pattern checks for stale or missing documentation to maintain link integrity.