neb-doc-maintenance

Detect documentation drift against git history and open a PR.

Updated Aug 27, 2026

Search Tags:#documentation #audit #governance #drift #branch #pull-request #git-history

Ready to run

npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-doc-maintenance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: neb-doc-maintenance
Source: https://github.com/nebinfra/nebcore-ai-skills/tree/main/neb-doc-maintenance
Command: npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-doc-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit top-level documentation (README, SPEC, PRODUCT) against recent git history to identify drift where features are missing from docs or upcoming features have landed. Proposes minimal edits, creates a branch, and opens a PR. Use when asked to review docs for accuracy, after major feature merges, or on a periodic schedule.

Core Features & Use Cases

Drift detection across README, SPEC, and PRODUCT by comparing against recent commits and shipped features.
Automated drift plan generation that surfaces exact edits and a PR-ready branch, with a minimal-change approach.
Governance-safe workflow that preserves voice and formatting while updating the central drift cursor for future reviews.

Quick Start

Trigger the doc-maintenance skill to detect drift, generate a drift summary, and open a PR with minimal edits.

Frequently Asked Questions about neb-doc-maintenance

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

FAQPage Schema

How do I detect documentation drift against recent git history?▼

Detect documentation drift by comparing top-level README, SPEC, and PRODUCT files against recent git commits. The process surfaces a concise drift report identifying where shipped features are missing from docs or upcoming features have already landed.

What is the best way to auto-suggest minimal edits for outdated documentation?▼

Auto-suggesting minimal edits for outdated documentation involves generating a targeted patch plan that preserves original voice and formatting. This approach aligns top-level docs with shipped features while keeping structural changes as small as possible.

How do I enforce a branch-and-PR workflow for documentation governance?▼

Enforce a branch-and-PR workflow for documentation governance by automatically creating a branch and opening a pull request with proposed edits. This ensures all documentation updates are reviewed before merging into the main repository.

When should I run a documentation audit for drift detection?▼

Run a documentation audit for drift detection after major feature merges or on a periodic schedule. This ensures top-level documents like README and SPEC remain accurate reflections of recently shipped code.

Does documentation drift detection preserve the existing formatting and voice?▼

Documentation drift detection preserves existing formatting and voice by enforcing a minimal-change approach. The generated patch plan updates content to align with shipped features without altering the original structural style.