documentation-consistency

Compare project documents and generate a structured inconsistency report.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dczmer/skill-issues --skill documentation-consistency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documentation-consistency
Source: https://github.com/dczmer/skill-issues/tree/main/skills/documentation-consistency
Command: npx skills add https://github.com/dczmer/skill-issues --skill documentation-consistency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and resolve inconsistencies across project documentation to ensure alignment and reduce drift.

Core Features & Use Cases

  • Cross-document comparison across README.md, PROJECT_PLAN.md, AGENTS.md, and flake.nix.
  • Automated detection of mismatches and generation of a structured report with recommendations.
  • Use Case: When a project updates its architecture or setup process, run this skill to surface misalignments and propose fixes.

Quick Start

Run the documentation consistency check to compare core docs and generate an actionable report.

Frequently Asked Questions about documentation-consistency

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

FAQPage Schema
How do I check for inconsistencies across project documentation?

Cross-document audits require comparing files like README.md, PROJECT_PLAN.md, AGENTS.md, and flake.nix to detect mismatches. This process generates a structured report with findings and alignment recommendations.

What is the best way to audit documentation drift after an architecture update?

Auditing documentation drift requires cross-file comparisons across project docs to surface misalignments. Running a consistency check proposes fixes and generates a structured report with actionable recommendations.

Can I use a documentation consistency check for projects with multiple markdown files?

Yes, documentation consistency checks apply to projects with multiple markdown files like README.md, PROJECT_PLAN.md, and AGENTS.md. Cross-file comparisons validate alignment and generate a structured findings report.

How do I verify that my flake.nix configuration matches my project documentation?

Verifying flake.nix alignment requires cross-file comparisons against project markdown docs like README.md. Rule checks identify configuration mismatches and generate a structured report with proposed fixes.

What does a documentation consistency report include?

A documentation consistency report includes cross-file comparison findings and rule check results. It provides structured recommendations to resolve mismatches across project docs like README.md and PROJECT_PLAN.md.

When do I need to run a cross-document validation check?

Cross-document validation is needed when updating project architecture or setup processes. It ensures core docs like README.md and AGENTS.md remain aligned, detecting drift through structured rule checks.