docs-index-keeper

Generate or update docs/README.md index rows from staged Markdown files.

4|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/oleg-koval/docs-index-keeper --skill docs-index-keeper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-index-keeper
Source: https://github.com/oleg-koval/docs-index-keeper/tree/main
Command: npx skills add https://github.com/oleg-koval/docs-index-keeper --skill docs-index-keeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

docs-index-keeper prevents missed or outdated entries in a repository’s Markdown docs index (commonly docs/README.md) by automatically updating the table as new or changed docs are added.

Core Features & Use Cases

  • Pre-commit and CI-friendly indexing: Install once to update docs index tables on staged Markdown changes and use a CI check that fails when the index is out of date.
  • Staged-file driven updates: Updates and checks operate on staged .md files so the index stays aligned with what’s actually going into the next commit.
  • Manual bulk indexing: Add one or many docs entries, including via quoted glob-like masks, so maintainers don’t edit index rows by hand.
  • Purpose extraction from headings: Populates the index “Purpose” column using the first Markdown heading in each doc (or a sensible fallback from the filename).

Quick Start

Run this instruction: Install docs-index-keeper in the repo and then initialize it with npx docs-index-keeper init so future pre-commit runs keep docs/README.md updated automatically.

Frequently Asked Questions about docs-index-keeper

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

FAQPage Schema
How do I automatically update a Markdown documentation index in Git?

To automatically update a Markdown documentation index in Git, use a pre-commit hook that reads staged Markdown files and inserts missing table rows into docs/README.md. This keeps your index synced with committed changes without manual editing.

What is the best way to keep a docs README table synchronized with new Markdown files?

Keeping a docs README table synchronized is best handled by CI enforcement that fails non-zero when the index is outdated. It scans staged Markdown inputs, filters to a configurable docs directory, and extracts purpose from the first heading to populate rows.

Can I use a pre-commit hook to manage my docs index table entries?

Yes, you can use a pre-commit hook to manage docs index table entries. Install the hook once, and it will automatically generate or update docs/README.md rows based on newly added or changed Markdown files during the staging process.

Do I need Node.js 18 to run Markdown indexing automation in CI?

Yes, you need Node.js 18 or higher to run this Markdown indexing automation in CI. The tool requires this environment to read staged Markdown inputs, apply directory excludes, and insert missing entries into a compatible Markdown table.

How do I add multiple Markdown files to a docs index at once?

To add multiple Markdown files to a docs index at once, use manual bulk indexing with quoted glob-like path masks. This allows maintainers to insert many documentation entries into the index table simultaneously without editing rows by hand.