tumiki-docs-update-guide

Document changes to skills and CLAUDE.md files after implementation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/rayven122/tumiki --skill tumiki-docs-update-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tumiki-docs-update-guide
Source: https://github.com/rayven122/tumiki/tree/main/.claude/skills/tumiki-docs-update-guide
Command: npx skills add https://github.com/rayven122/tumiki --skill tumiki-docs-update-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps post-implementation documentation in sync with feature changes by guiding the update of skills docs and CLAUDE.md, including change-detection, timing, and example-writing practices.

Core Features & Use Cases

  • Detect changes across skill source files and CLAUDE.md to trigger documentation updates, ensuring alignment between code, usage instructions, and references.
  • Provide a repeatable workflow for updating documentation, including when to refresh examples and how to annotate changes for future audits.
  • Support teams by reducing drift between implemented features and public-facing docs, improving maintainability and onboarding.

Quick Start

Review the latest changes in a feature update and trigger the documentation alignment process for skills and CLAUDE.md.

Frequently Asked Questions about tumiki-docs-update-guide

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

FAQPage Schema
How do I keep documentation in sync with code updates after implementation?

Documentation sync requires detecting changes in source files and CLAUDE.md, then applying structured update workflows to refresh usage instructions, code examples, and references. This reduces drift between implemented features and public-facing docs.

When should I update CLAUDE.md after modifying skill workflows?

Update CLAUDE.md when change-detection identifies modifications in skill source files. Timing guidance triggers the documentation alignment process immediately after feature updates to ensure references and usage instructions match the latest code.

What is the best way to format code examples in post-implementation docs?

Code-example formatting is enforced as a core requirement during documentation updates. The workflow applies specific formatting rules to examples within skills docs and CLAUDE.md to maintain consistency and support future audits.

How do I document changes to skills for future audits?

Annotate changes during the documentation update process by following the repeatable workflow. This includes tracking detected modifications, updating examples, and applying update procedures that create a clear record for auditing purposes.

Does this documentation update workflow support team onboarding?

Yes, the workflow reduces drift between implemented features and public-facing docs, which directly improves maintainability and onboarding. Teams use the change-detection and timing guidance to keep documentation accurate for new members.

What are the limitations of using change-detection for documentation updates?

Change-detection focuses specifically on skill source files and CLAUDE.md alignment. It requires reviewing the latest feature changes before triggering the documentation process and does not automatically generate new documentation from scratch.