Can I integrate this into my CI/CD pipeline?

Yes, the skill is designed with a Layer 1 defense that uses pytest to automatically fail builds if documentation is out of sync with the code.

Does it work with local language models?

Yes, this skill is part of the anyclaude-local repository which is optimized for use with LM Studio and local LLM environments.

Which files does this skill monitor?

It monitors README.md, SYNC-STATUS.md, UPDATES.md, marketplace.json, and various installation templates to ensure uniform reporting.

How does this skill detect documentation drift?

It scans your directory structure for actual assets like skills, agents, and commands, then compares those counts against the numbers documented in your README.md and other metadata files.

What are the four layers of defense mentioned?

The strategy includes Layer 1: Automated Tests, Layer 2: Agent Memory (doc-master), Layer 3: Optional Pre-commit Hooks, and Layer 4: Real-time Auto-reminders.

Consistency Enforcement

Name: Consistency Enforcement
Author: akaszubski

byakaszubski

•

Content Management

Prevents documentation drift by synchronizing README files, metrics, and project metadata with the actual codebase state.

About

The Consistency Enforcement skill establishes a robust four-layer defense system designed to eliminate documentation drift in complex software projects. It automatically monitors directories for skills, agents, and commands, ensuring that counts and references in README.md, marketplace.json, and status reports always match reality. By integrating automated testing, pre-commit hooks, and real-time reminders, it helps maintain a single source of truth and prevents user confusion caused by stale documentation or broken references.

Key Features

Cross-document synchronization for README, status files, and marketplace metadata
2 GitHub stars
Four-layer defense strategy including CI/CD tests and pre-commit validation
Automated verification of skill, agent, and command counts
Pre-configured shell commands for rapid directory audits
Auto-activation triggers during documentation updates and git workflows

Use Cases

Automating documentation audits during high-velocity development cycles
Preventing broken references when deprecating or renaming repository assets
Maintaining accurate metrics in public plugin marketplaces and directories

About

Key Features

Cross-document synchronization for README, status files, and marketplace metadata
2 GitHub stars
Four-layer defense strategy including CI/CD tests and pre-commit validation
Automated verification of skill, agent, and command counts
Pre-configured shell commands for rapid directory audits
Auto-activation triggers during documentation updates and git workflows

Use Cases

Automating documentation audits during high-velocity development cycles
Preventing broken references when deprecating or renaming repository assets
Maintaining accurate metrics in public plugin marketplaces and directories