document

Detect documentation drift and patch stale project docs to match the current codebase.

Updated Jun 22, 2026

Search Tags:#documentation #codebase #drift detection #readme #status tracking #claude md

Ready to run

npx skills add https://github.com/Elad73/agentic-base-layer --skill document-elad73

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: document
Source: https://github.com/Elad73/agentic-base-layer/tree/main/global/skills/document
Command: npx skills add https://github.com/Elad73/agentic-base-layer --skill document-elad73

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fixes documentation drift by comparing the codebase to project docs and updating the docs so they reflect what the project actually is today.

Core Features & Use Cases

Drift Detection: Scans code, project status files, and common doc surfaces to spot mismatches in facts, structure, and workflow.
Targeted Doc Repairs: Applies small, surgical edits to README, CLAUDE.md, and STATUS.md instead of rewriting everything.
Safety Check Before Writing: Searches documentation for secrets before making any changes, helping prevent accidental leakage.
Use Case: After shipping a feature, use this Skill to refresh the project’s docs so setup steps, commands, and current state stay accurate.

Quick Start

Ask the skill to scan the repository for documentation drift and update the relevant docs to match the current codebase.

Frequently Asked Questions about document

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

FAQPage Schema

How do I fix documentation drift after updating my codebase?▼

To fix documentation drift, scan your codebase against existing project docs and apply targeted patches to stale files. This process detects mismatches in facts and workflow, surgically updating docs to reflect current reality without rewriting everything.

What is the best way to keep a README in sync with code changes?▼

The best way to keep a README in sync is performing source-of-truth scanning to spot factual mismatches, then applying targeted edits that preserve existing structure. This ensures setup steps and commands stay accurate after shipping new features.

Can I update CLAUDE.md and STATUS.md files without rewriting the whole document?▼

Yes, you can update CLAUDE.md and STATUS.md files without a full rewrite by applying surgical, targeted edits. This method preserves the existing document structure while correcting outdated facts to match the current codebase.

Does updating project documentation risk exposing secrets in the codebase?▼

Updating project documentation does not expose secrets when a pre-write safety check is performed. The system searches documentation surfaces for secrets before making any changes, helping prevent accidental leakage during the patch process.

When do I need to scan a repository for documentation drift?▼

You need to scan a repository for documentation drift during release preparation and after shipping post-feature updates. It is necessary whenever project status files or common doc surfaces no longer reflect the actual codebase reality.