project-consolidate-documentation

Audit Documentation/ for governance rule deviations and generate a remediation report.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/cslsoftwares/ParamentersORM --skill project-consolidate-documentation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-consolidate-documentation
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/project-consolidate-documentation_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill project-consolidate-documentation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits Documentation/ to enforce canonical structure, versioning, naming conventions, and hub/changelog presence, enabling consistent, maintainable documentation.

Core Features & Use Cases

  • Verifies versioning on Documentation/ assets using FileVersion markers and hub references.
  • Checks for broken links and canonical navigation across Documentation/.
  • Enforces naming conventions across Analise, Arquitetura, BancoDados, RegrasNegocio, Roteiro, and Versionamento.
  • Produces a remediation report to guide documentation teams.

Quick Start

Run the consolidation to audit Documentation/ and generate a compliance report.

Frequently Asked Questions about project-consolidate-documentation

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

FAQPage Schema
How do I audit documentation for versioning and link integrity?

To audit documentation, you can run a consolidation check that scans the Documentation/ hierarchy to verify versioning markers, validate link integrity, and identify structural deviations from governance rules.

What is the best way to enforce naming conventions across technical documentation?

Enforcing naming conventions requires auditing your Documentation/ structure to ensure folders like Analise, Arquitetura, BancoDados, RegrasNegocio, Roteiro, and Versionamento comply with canonical rules, producing a structured remediation report.

Does documentation auditing work without setting up dependencies?

Yes, documentation auditing runs without external dependencies, directly scanning your Documentation/ directory to apply seven canonical checks and generate a compliance report.

How do I generate a remediation report for broken links in documentation?

Generating a remediation report involves scanning your Documentation/ directory for broken links and canonical navigation issues, which outputs concrete steps for resolving link integrity and structural deviations.

Why does my documentation audit show deviations in hub and changelog presence?

Documentation audits flag hub and changelog deviations because canonical governance rules require specific hub references and version markers to maintain consistent, navigable documentation structures.

What are the limitations of automated documentation compliance checks?

Automated documentation compliance checks are limited to verifying structural rules, versioning markers, and link integrity within the Documentation/ hierarchy, and do not evaluate the semantic accuracy of the content itself.