update-docs

Scan recent codebase changes and update CLAUDE.md documentation files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of updating CLAUDE.md documentation files, ensuring that project documentation stays synchronized with codebase changes and reducing manual maintenance overhead.

Core Features & Use Cases

  • Change Detection: Identifies recent modifications in the codebase.
  • Documentation Mapping: Maps specific code changes to relevant CLAUDE.md files for updates.
  • Content Management: Guides on adding new entries, removing stale references, and maintaining conciseness.
  • Use Case: After adding a new API endpoint, this Skill can automatically update the src/app/api/CLAUDE.md file to reflect the new route and its purpose.

Quick Start

Run the update-docs skill to scan recent changes and update CLAUDE.md files.

Frequently Asked Questions about update-docs

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

FAQPage Schema
How do I keep CLAUDE.md documentation up-to-date with codebase changes?

Updating CLAUDE.md documentation involves scanning recent Git diffs to identify new features, modules, and schema modifications, then mapping those code changes to relevant Markdown files for content updates.

How does automated documentation mapping work for new API endpoints?

Automated documentation mapping detects code modifications like new API endpoints and maps those changes to specific CLAUDE.md files, guiding the addition of new entries and removal of stale references to maintain consistency.

Do I need Git to automate updating CLAUDE.md files?

Yes, Git is required to identify code differences and recent modifications in the codebase, which enables the structured process of updating Markdown documentation to reflect new features and schema changes.

What's the best way to maintain documentation consistency across database schemas?

The best way to maintain documentation consistency is automating the detection of schema modifications and codebase changes, then systematically updating CLAUDE.md files to accurately reflect those new database schemas and modules.

When should I avoid automating project documentation updates?

You should avoid automating project documentation updates if your codebase lacks Git version control for change detection, or if your documentation format does not follow the CLAUDE.md Markdown structure required for mapping.