doc-update

Automates updating documentation across specified folders and file types after code changes.

Updated Feb 9, 2026

Search Tags:#documentation #project-docs #docs-sync #ai-docs #code-diff #documentation-update

Ready to run

npx skills add https://github.com/andrewnovykov/total-66 --skill doc-update-andrewnovykov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-update
Source: https://github.com/andrewnovykov/total-66/tree/main/.claude/skills/doc-update
Command: npx skills add https://github.com/andrewnovykov/total-66 --skill doc-update-andrewnovykov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams keep project documentation in sync with code changes by automatically analyzing diffs and updating documentation artifacts across .ai_docs, project_doc, and references.

Core Features & Use Cases

Analyzes code changes to identify impacted documentation across schemas, contexts, APIs, and design docs.
Applies updates to .ai_docs and project_doc to reflect new or changed functionality.
Supports a real-world workflow where a feature, bug fix, or schema change triggers documentation synchronization.

Quick Start

Run the doc-update skill after completing a feature or bug fix to align code changes with all project documentation.

Frequently Asked Questions about doc-update

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

FAQPage Schema

How do I automatically update project documentation when code changes?▼

To update project documentation when code changes, you can analyze code diffs to identify impacted schemas, APIs, and design docs, then apply those changes across .ai_docs and project_doc sections to keep everything in sync.

What is the best way to keep .ai_docs files synchronized with schema updates?▼

Keeping .ai_docs synchronized with schema updates involves analyzing code diffs to detect schema changes and applying those updates directly to schema tables, context docs, and design pages with built-in validation and error handling.

How does analyzing code diffs help with documentation synchronization?▼

Analyzing code diffs helps with documentation synchronization by identifying exactly which features, bug fixes, or schema changes occurred, allowing targeted updates to API docs, references, and data-model sections without manual review.

When do I need to update API docs and design pages after a feature release?▼

You need to update API docs and design pages after a feature release whenever code changes introduce new functionality, fix bugs, or alter data models, ensuring project_doc and references accurately reflect the current codebase.

Does automatic documentation update work for both bug fixes and new features?▼

Automatic documentation update works for both bug fixes and new features by analyzing the underlying code diff for either type of change and applying the necessary updates across all impacted documentation artifacts.

What are the limitations of syncing project docs with code changes automatically?▼

A limitation of syncing project docs automatically is that it relies on analyzing code diffs, meaning documentation accuracy depends on the clarity of the diff and may require validation to ensure complex design pages and contexts are correctly updated.