docs-architecture-drift-check

Compare documented module structures and file paths against the actual codebase.

Updated Aug 27, 2026

Search Tags:#architecture #documentation #codebase #drift detection #verification #code sync

Ready to run

npx skills add https://github.com/roaming-rockenfels/ghostfolio --skill docs-architecture-drift-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs-architecture-drift-check
Source: https://github.com/roaming-rockenfels/ghostfolio/tree/main/.claude/skills/docs-architecture-drift-check
Command: npx skills add https://github.com/roaming-rockenfels/ghostfolio --skill docs-architecture-drift-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automatically detects and reports discrepancies between your project's documentation and its actual codebase, preventing outdated information from causing confusion.

Core Features & Use Cases

Module Tree Verification: Compares the documented module structure against the files present in the codebase.
Responsibility Documentation Check: Ensures that the described functions and behaviors in responsibility documents accurately reflect the code.
Verification Documentation Audit: Validates that documented verification tiers and checks align with the actual implementation and evaluation data.
Use Case: After a developer implements a new feature, this Skill can be run to ensure the architecture diagrams and responsibility descriptions in the documentation are updated accordingly, flagging any drift before it becomes a problem.

Quick Start

Run the docs-architecture-drift-check skill to verify documentation accuracy against the current codebase.

Frequently Asked Questions about docs-architecture-drift-check

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

FAQPage Schema

How do I detect documentation drift between my codebase and module docs?▼

Detect documentation drift by comparing documented module structures, file paths, and described behaviors against the actual codebase to automatically report discrepancies and prevent outdated information.

What is documentation drift verification for module trees?▼

Documentation drift verification for module trees is the process of comparing the documented module structure against the actual files present in the codebase to ensure architectural accuracy.

How do I verify responsibility documentation matches the actual code behaviors?▼

Verify responsibility documentation by checking that the described functions and behaviors in your responsibility documents accurately reflect the code's actual implementation and current logic.

Do I need specific documentation files to run a code sync verification check?▼

You need specific documentation files and the codebase's file structure available for comparison to run a code sync verification check and validate accuracy in module trees and verification procedures.

When should I run a documentation drift detection check on my project?▼

Run documentation drift detection checks after a developer implements a new feature to ensure architecture diagrams and responsibility descriptions are updated, flagging any drift before it causes confusion.