consistency-enforcement

Validate README.md counts and cross-references against the codebase.

32|5|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/akaszubski/autonomous-dev --skill consistency-enforcement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consistency-enforcement
Source: https://github.com/akaszubski/autonomous-dev/tree/main/plugins/autonomous-dev/skills/consistency-enforcement
Command: npx skills add https://github.com/akaszubski/autonomous-dev --skill consistency-enforcement

SYSTEM DOCUMENTATION & REQUIREMENTS

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?"

Frequently Asked Questions about consistency-enforcement

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

FAQPage Schema
How do I prevent documentation drift between my README and codebase?

Documentation drift occurs when README counts and cross-references become outdated as code changes. This skill automatically validates that skill, agent, and command counts in README.md match your actual codebase, triggering reminders during commits and marketplace updates to keep documentation synchronized.

How do I ensure my documentation stays consistent across multiple files?

Cross-document consistency validation checks README.md, SYNC-STATUS.md, marketplace.json, and related files simultaneously. This skill enforces synchronization across all documentation during updates, removals, and additions, ensuring metrics and references remain aligned throughout your project.

What happens when I add or remove a skill from my codebase?

When you add or remove a skill, this skill auto-activates to remind you to update all related documentation and marketplace.json. It provides step-by-step workflows and validates that counts are updated everywhere, preventing embarrassing discrepancies in your marketplace listings.

Can I validate documentation consistency before making a commit?

Yes. Run the validation hook with `python plugins/autonomous-dev/hooks/validate_docs_consistency.py` before committing. This performs a consistency check across all documentation files and codebase counts, catching drift before it reaches your repository.

What documentation files does this skill check?

This skill monitors README.md as the source of truth alongside SYNC-STATUS.md, marketplace.json, and other key documentation files. It validates skill, agent, and command counts plus cross-references across all synchronized documentation.

Does this skill work automatically or do I need to run it manually?

It auto-activates on relevant keywords like readme, commit, skill, agent, command, and update. It also provides a manual validation hook you can run before commits to proactively catch documentation drift.