claude-md-sync

Analyze codebase changes since the last CLAUDE.md update and summarize impact.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/wzh274728277/claude-md-sync --skill claude-md-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-md-sync
Source: https://github.com/wzh274728277/claude-md-sync/tree/main
Command: npx skills add https://github.com/wzh274728277/claude-md-sync --skill claude-md-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

CLAUDE.md often becomes outdated as the codebase evolves. This Skill monitors commits since the last CLAUDE.md update and helps keep the documentation in sync with project changes.

Core Features & Use Cases

  • Analyze recent commits affecting CLAUDE.md to surface when documentation is out-of-date.
  • Categorize changes by type and component, so engineers can quickly identify what to update.
  • Generate a concise update plan for CLAUDE.md, with optional JSON output for programmatic processing.

Quick Start

Run the analysis script to review commits since the last CLAUDE.md update and propose corresponding CLAUDE.md changes.

Frequently Asked Questions about claude-md-sync

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

FAQPage Schema
How do I keep CLAUDE.md documentation in sync with codebase changes?

To keep CLAUDE.md in sync, analyze recent git commits to detect new directories, API changes, and documentation gaps, then generate a human-readable summary of impacts to update the markdown file.

What is the best way to detect when project documentation is out of date?

The best way to detect outdated documentation is to monitor git commit history since the last CLAUDE.md update and categorize codebase changes by component to surface documentation gaps.

How do I automatically generate an update plan for markdown documentation?

Automatically generate a markdown update plan by analyzing codebase evolution, categorizing recent changes, and outputting a concise summary or optional JSON for programmatic processing.

Can I get a JSON output of codebase changes for programmatic processing?

Yes, you can get JSON output of codebase changes by running the analysis script to summarize architectural shifts and documentation gaps into optional JSON format for programmatic processing.

Does the documentation sync script require git to track codebase evolution?

Yes, the documentation sync script uses git to track codebase evolution, monitoring commits since the last CLAUDE.md update to identify when architectural or API changes require documentation updates.