consistency-enforcement

What problem does it solve?

Documentation often drifts from the actual codebase, leading to user confusion, wasted time, and a lack of trust in project information. This skill acts as a "Layer 4 Defense" to automatically remind you to maintain consistency across all documentation, especially counts of skills, agents, and commands.

Core Features & Use Cases

• README.md as Source of Truth: Ensures all counts (skills, agents, commands) in README.md accurately match the actual number of resources in the codebase.
• Cross-Document Sync: Verifies consistency across README.md, SYNC-STATUS.md, marketplace.json, and other key documentation files.
• Drift Prevention Workflows: Provides clear, step-by-step workflows for adding, removing, or updating skills, ensuring all related documentation is synchronized.
• Use Case: When you add a new skill, this skill will automatically remind you to update all relevant documentation files and marketplace.json, ensuring your project's public-facing information is always accurate.
• Use Case: Prevent embarrassing discrepancies in your project's marketplace listings by automatically validating metrics against the actual codebase.

Quick Start

This is a knowledge skill, auto-activated by relevant keywords.

To verify consistency before a commit:

python plugins/autonomous-dev/hooks/validate_docs_consistency.py

Or simply ask:

"How do I ensure my documentation counts are consistent?"