update-documentation

Audit session activity and code changes to recommend documentation updates.

3|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/kitaekatt/plugins-kit --skill update-documentation-kitaekatt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-documentation
Source: https://github.com/kitaekatt/plugins-kit/tree/main/plugins/skills-kit/skills/update-documentation
Command: npx skills add https://github.com/kitaekatt/plugins-kit --skill update-documentation-kitaekatt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of documentation decay by capturing valuable session insights, code changes, and error resolutions before they are forgotten, ensuring project knowledge remains current and actionable.

Core Features & Use Cases

  • Session Audit: Automatically reviews git diffs and conversation history to identify documentation gaps.
  • Intelligent Classification: Categorizes findings into root CLAUDE.md, directory-specific docs, or skill references based on impact and scope.
  • Use Case: After refactoring a complex module and resolving several integration errors, use this skill to generate a summary of the new interface and error-avoidance tips for future developers.

Quick Start

Run the update-documentation skill at the end of your session to review your work and suggest necessary updates to the project documentation.

Frequently Asked Questions about update-documentation

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

FAQPage Schema
How do I update project documentation after a coding session?

To update project documentation after a coding session, run this skill to audit your git diffs and conversation history, automatically identifying and recommending necessary updates to root CLAUDE.md files and directory-specific docs.

What is the best way to prevent documentation decay in a project?

Preventing documentation decay requires capturing session insights, code changes, and error resolutions before they are forgotten. This skill audits session activity and classifies findings into project-wide or directory-specific documentation to keep knowledge current.

How does session audit work for technical writing and knowledge management?

Session audit for technical writing works by automatically reviewing git diffs and conversation history to identify documentation gaps, categorizing findings based on impact and scope to improve future session efficiency.

Do I need any dependencies to audit session activity for project maintenance?

No dependencies are required to audit session activity for project maintenance. The skill operates independently to review your session activity and suggest structured updates to CLAUDE.md files and skill references.

Can I document error resolutions and code changes for specific directories?

Yes, you can document error resolutions and code changes for specific directories. The skill intelligently classifies findings into root CLAUDE.md files, directory-specific docs, or skill references based on their impact and scope.