doc-sentinel

Reconcile Markdown document bindings with source code across Git repositories.

6|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/northseadl/norix-skills --skill doc-sentinel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-sentinel
Source: https://github.com/northseadl/norix-skills/tree/main/doc-sentinel
Command: npx skills add https://github.com/northseadl/norix-skills --skill doc-sentinel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Synchronizes documentation with source code by binding Markdown docs to the repository's file tree and git history, enabling traceability and reducing stale information.

Core Features & Use Cases

  • Identity binding: embed doc_id, source_paths, and tree hash in frontmatter to establish a trustworthy mapping.
  • Change reconciliation: compute git diffs and create PlanItems with confidence and risk metadata to guide updates.
  • Idempotent execution: apply plans safely to update statuses and paths while keeping history.

Quick Start

Install the Doc Sentinel skill in your repository and run the sentinel status command to begin binding documents to their source code.

Frequently Asked Questions about doc-sentinel

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

FAQPage Schema
How do I keep Markdown documentation in sync with source code across git repositories?▼

Documentation change reconciliation computes git diffs to generate actionable change plans with confidence and risk metadata, guiding safe updates while keeping history. This mechanism ensures documentation stays aligned with source code modifications.

How do I generate a change plan for outdated documentation based on git diffs?▼

Idempotent execution applies generated change plans safely to update document statuses and paths while preserving repository history. This ensures documentation reconciliation operations can be run repeatedly without causing duplicate or conflicting modifications.

Do I need Markdown frontmatter to bind documents to a repository file tree?▼

Install the skill in your repository and run the sentinel status command to begin binding documents to their source code. This initial check surfaces actionable changes and establishes the baseline frontmatter bindings for ongoing reconciliation.

What is the best way to track document-code binding risks before applying updates?▼

Identity binding establishes traceability by embedding doc_id, source_paths, and tree hash in Markdown frontmatter. This creates a verifiable link between documentation and the repository file tree, reducing stale information and enabling accurate change reconciliation.