shrink-doc

Compress documentation while preserving YAML frontmatter and execution equivalence.

101|2|Updated Jan 7, 2026

Search Tags:#automation #versioning #documentation #validation #baseline #compress #execution-equivalence

Ready to run

npx skills add https://github.com/cowwoc/cat --skill shrink-doc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shrink-doc
Source: https://github.com/cowwoc/cat/tree/main/plugin/skills/shrink-doc
Command: npx skills add https://github.com/cowwoc/cat --skill shrink-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compress documentation to reduce size while preserving execution behavior across versions and validation baselines.

Core Features & Use Cases

Validation-driven compression that preserves YAML frontmatter and essential decision data
Versioned outputs with persistent baselines for safe rollback
Automated workflow that compares compressed output against original to ensure execution equivalence

Quick Start

Use the shrink-doc skill to compress the target document and verify equivalence against the original baseline.

Frequently Asked Questions about shrink-doc

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

FAQPage Schema

How do I compress documentation without changing runtime behavior?▼

You can compress documentation without changing runtime behavior by using a validation-driven workflow that compares compressed output against an original baseline to ensure execution equivalence.

What does execution equivalence mean when compressing docs?▼

Execution equivalence means the compressed document produces identical runtime outcomes to the original, verified by comparing output against a persistent validation baseline to guarantee no behavioral changes.

How do I preserve YAML frontmatter when reducing documentation size?▼

To preserve YAML frontmatter when reducing documentation size, use a compression workflow that explicitly enforces the retention of YAML frontmatter, decision data, and execution flow during the reduction process.

Can I roll back compressed documentation to a previous version?▼

Yes, you can roll back compressed documentation because the compression process generates versioned outputs with persistent validation baselines, ensuring safe rollback to any prior document state.

What is the best way to validate that compressed docs match the original?▼

The best way to validate compressed docs is through an automated workflow that compares the compressed output against the original baseline to guarantee identical execution outcomes and behavioral equivalence.

When should I not use validation-driven documentation compression?▼

You should avoid validation-driven documentation compression when your document set does not require exact runtime behavior preservation or lacks the baseline data needed to verify execution equivalence.