docs-update-all

Synchronize project documentation with codebase changes and produce an auditable change log.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/ManfronEnrico/thesis-manifold --skill docs-update-all
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-update-all
Source: https://github.com/ManfronEnrico/thesis-manifold/tree/main/.claude/skills/docs-update-all
Command: npx skills add https://github.com/ManfronEnrico/thesis-manifold --skill docs-update-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates and synchronizes all living project documentation after major work, ensuring thesis sections, compliance records, CLAUDE hubs, cheatsheets, READMEs, and planning artifacts stay aligned with code changes.

Core Features & Use Cases

  • Automated cross-document synchronization: updates thesis sections, README files, cheatsheets, CLAUDE.md, and plans after changes.
  • Compliance and frozen-decision tracking: cascades updates to formal requirements and workflow references.
  • Trigger-based updates and staged execution: runs only affected documents to minimize churn.

Quick Start

Run /update-all-docs to synchronize all affected documents.

Frequently Asked Questions about docs-update-all

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

FAQPage Schema
How do I automate project documentation updates after codebase changes?

Automate project documentation updates by running a sync command that coordinates and revises all living documents to reflect the latest codebase changes, ensuring full consistency across the project.

What is cross-document synchronization for thesis and compliance artifacts?

Cross-document synchronization cascades codebase edits across thesis sections, compliance records, CLAUDE.md hubs, and cheatsheets, ensuring formal requirements and workflow references stay aligned with code changes.

How do I keep my README and planning docs consistent with code edits?

Keep README and planning docs consistent by triggering automated staged execution that runs only affected documents after edits, minimizing churn while updating plans and README files to match.

Can I generate an auditable change log for documentation updates?

Generate an auditable change log for documentation updates by executing a full sync that applies Read, Write, and Grep-like validations, producing traceable records of all modifications made to project artifacts.

Does this documentation sync tool support frozen-decision tracking?

This documentation sync tool supports frozen-decision tracking by cascading updates to formal requirements and compliance notes, ensuring frozen decisions and workflow references remain accurately reflected after codebase modifications.

When should I avoid running a full project documentation sync?

Avoid running a full project documentation sync when only minor unrelated edits occur, as the tool's trigger-based staged execution is designed to run only affected documents, minimizing unnecessary churn across artifacts.