Detect documentation drift against git history and open a PR.
npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-doc-maintenance
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
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.
Trigger the doc-maintenance skill to detect drift, generate a drift summary, and open a PR with minimal edits.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
tamziAudit top-level documentation against recent git history and open pull requests.
elijahbowieCompare documentation against recent git commits and generate a pull request.
brenordvGenerate standardized pull-request descriptions from git diffs and commit history.
srirajkAnalyze git history to produce a structured PR risk profile.
