upd-docs

Map changed source files to relevant docs via aggregator indexes and dispatch parallel agents.

11|Updated Mar 19, 2019
One-click install
npx skills add https://github.com/lukoshkin/evangelist --skill upd-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upd-docs
Source: https://github.com/lukoshkin/evangelist/tree/main/conf/ai/claude/skills/upd-docs
Command: npx skills add https://github.com/lukoshkin/evangelist --skill upd-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when updating project documentation after code changes — maps changed source files to relevant docs via aggregator indexes, then dispatches parallel agents to update each doc. Requires README.md aggregators with Key Files columns in each docs subdirectory.

Core Features & Use Cases

  • Automatically map code changes to documentation topics using per-directory README aggregators.
  • Dispatch parallel agents to update multiple docs in response to a single change set.
  • Supports end-to-end documentation maintenance across docs/* directories with automated consistency checks.

Quick Start

Run the upd-docs workflow to scan changed code and update corresponding docs via aggregators.

Frequently Asked Questions about upd-docs

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

FAQPage Schema
How do I automate documentation updates when source code changes?

Documentation updates are automated by mapping changed source files to relevant docs via aggregator indexes and dispatching parallel agents to update each doc automatically.

What are aggregator indexes and how do they map code changes to docs?

Aggregator indexes are README.md files in docs subdirectories containing Key Files tables that map code paths to documentation, enabling automated discovery and parallelized updates.

Do I need a specific directory structure to automate docs updates from diffs?

Yes, repositories must have docs organized under docs/* directories with README.md aggregators containing Key Files columns in each subdirectory to map code paths to docs.

Can I update multiple documentation files in parallel after a single code change?

Yes, parallel agents are dispatched to update multiple docs simultaneously in response to a single change set, applying automated consistency checks across docs/* directories.

What is the best way to maintain documentation consistency across a large project?

The best way is using diff-based change detection with per-directory README aggregators to map code changes, then dispatching parallel agents for end-to-end documentation maintenance.

When should I not use automated aggregator-based docs updates?

This approach is not suitable for repositories lacking docs/* directory organization or README.md aggregators with Key Files tables, as these structures are required for code-to-doc mapping.