update-docs

Detect discrepancies between public documentation and internal code conventions.

74|14|Updated Jan 20, 2026

Search Tags:#documentation #verification #review #docs #drift #update #code-conformity

Ready to run

npx skills add https://github.com/ActiveMemory/ctx --skill update-docs-activememory

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-docs
Source: https://github.com/ActiveMemory/ctx/tree/main/.claude/skills/update-docs
Command: npx skills add https://github.com/ActiveMemory/ctx --skill update-docs-activememory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps documentation aligned with the latest code and configurations, preventing mismatches that confuse users and developers.

Core Features & Use Cases

Drift detection: identifies discrepancies between code behavior and public docs.
Mapping verification: ensures changes in code are reflected in docs indexes and guides.
Automation readiness: guides teams to update docs during review or CI workflows.

Quick Start

Run update-docs to verify that documentation aligns with the latest code changes.

Frequently Asked Questions about update-docs

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

FAQPage Schema

How do I detect documentation drift after code changes?▼

Documentation drift is detected by comparing public documentation against internal code conventions and user-facing behavior to identify and report discrepancies after changes are applied.

How do I verify docs mapping conforms to updated code conventions?▼

Docs mapping conformity is verified by validating affected packages, updating guides, and triggering self-maintenance reviews to ensure documentation indexes reflect the latest code behavior.

Can I automate documentation updates in my CI workflow?▼

Yes, automation readiness is supported by guiding teams to verify documentation alignment with the latest code and configurations during review or continuous integration workflows.

What is the best way to keep CLI interface documentation in sync?▼

The best way to keep CLI interface documentation in sync is applying drift detection workflows to source code and documentation artifacts where code changes affect user-facing behavior.

Does documentation review work for both source code and documentation artifacts?▼

Yes, documentation review targets both source code and documentation artifacts, ensuring mapping and style remain current by validating affected packages after code modifications.