update-docs

Automate documentation maintenance and synchronization with code changes.

5|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/sambeau/kanbanzai --skill update-docs-sambeau
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-docs
Source: https://github.com/sambeau/kanbanzai/tree/main/.kbz/skills/update-docs
Command: npx skills add https://github.com/sambeau/kanbanzai --skill update-docs-sambeau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation often drifts when code changes, leading to out-of-date guides and broken cross-references. This skill ensures the documentation stays current with implementation.

Core Features & Use Cases

  • Register new documents with doc(action: register) to onboard new content.
  • Refresh edited documents with doc(action: refresh) to update the content hash and tracking.
  • Audit and align changelogs, cross-references, and content currency across the project docs.

Quick Start

Register new documents with doc(action: register) and refresh edited ones with doc(action: refresh) to keep documentation aligned with the code.

Frequently Asked Questions about update-docs

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

FAQPage Schema
How do I keep documentation in sync with code changes automatically?

Documentation synchronization prevents drift by enforcing doc(action: register) for new files and doc(action: refresh) for edits, validating content hashes and cross-references against the current code implementation.

What is documentation drift and how do cross-references break?

Documentation drift occurs when project guides become out-of-date after code changes, leading to broken cross-references. Synchronization tools fix this by validating tracking hashes and aligning changelogs with the actual implementation.

How do I update a changelog and cross-references for an edited document?

To update a changelog and cross-references for an edited document, apply doc(action: refresh) to update the content hash and tracking, ensuring the documentation is audit-ready and aligned with the current code.

Can I audit multiple document versions for content currency?

Yes, you can audit content currency across multiple document versions by validating registered documents against the current code implementation, ensuring changelog updates and cross-references remain consistent.

Does this documentation synchronization approach require any external dependencies?

No, this documentation synchronization approach operates without external dependencies, relying entirely on internal doc(action: register) and doc(action: refresh) commands to maintain tracking and alignment.