claude-docs

Synchronize planning documentation and task boards by analyzing git diffs.

2|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/erclx/aitk --skill claude-docs-erclx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-docs
Source: https://github.com/erclx/aitk/tree/main/claude/skills/claude-docs
Command: npx skills add https://github.com/erclx/aitk --skill claude-docs-erclx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents documentation drift by automatically reconciling your project's planning documents with the actual changes shipped in your code, ensuring that task boards and architecture records remain accurate reflections of your work.

Core Features & Use Cases

  • Automated Reconciliation: Marks completed tasks as finished based on diffs and archives associated plans.
  • Drift Detection: Identifies stale diagrams and missing wireframe documentation when code structure changes.
  • Use Case: After completing a complex feature implementation, run this skill to automatically update your task board, archive the relevant design plans, and flag any architectural diagrams that need manual updates due to the new code.

Quick Start

Run the claude-docs skill to reconcile your current session changes with the project planning documentation.

Frequently Asked Questions about claude-docs

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

FAQPage Schema
How do I automatically sync planning docs with git changes?

To sync planning docs with git changes, analyze repository diffs to mark completed outcomes, archive plans, and detect stale artifacts. This prevents documentation drift by reconciling task boards with actual code modifications.

How does drift detection work for architectural diagrams?

Drift detection works by analyzing git diffs to identify stale diagrams and missing wireframe documentation when code structure changes. It flags architectural artifacts requiring manual updates due to new code modifications.

What is the best way to update a task board after shipping a feature?

The best way to update a task board after shipping is running automated reconciliation against git diffs. This marks completed tasks as finished and archives associated design plans based on actual code changes.

Do I need git integration to track file changes for documentation sync?

Yes, git integration is required to track file changes for documentation sync. It resolves merge bases and monitors working tree modifications to accurately reconcile planning documents with shipped code.

Can I detect stale design artifacts in the .claude directory structure?

Yes, you can detect stale design artifacts by operating on the .claude directory structure. The system analyzes git diffs to flag outdated architectural diagrams and missing wireframe documentation automatically.

When should I not use automated documentation reconciliation?

Automated documentation reconciliation should not be used without a git repository to analyze. It requires git integration to resolve merge bases and track file changes across the working tree for accurate drift detection.