doc-condenser

Condense technical documentation by applying a 40% length cap, converting metrics into scannable tables, and preserving all file paths and representative code snippets. It uses KEEP, CONDENSE, and REMOVE rules to reduce narrative overhead while maintaining structural clarity for engineering consumption.

Summarize a repository README by extracting architecture highlights and listing project-relative file paths. The process replaces long code examples with representative patterns and source references, producing a concise single-page implementation spec for quick reference.

Documentation condensing preserves all full or project-relative file paths and retains short illustrative code snippets intact. Long code examples are replaced with representative patterns plus source references to maintain technical accuracy while strictly enforcing the 40% length cap.

Yes, documentation summarization applies to software repositories, API references, design documents, and large text sources. It enforces structural preservation and clarity, making it suitable for any verbose technical text needing a concise, developer-focused specification.

The 40% length cap restricts output to less than half the original word count, meaning long narrative sections and extended code blocks are removed or condensed into representative patterns. Explicit KEEP, CONDENSE, and REMOVE rules govern what content survives the reduction process.

Yes, generating condensed developer specs requires following a referenced style guide for consistent table and header formatting. This ensures the condensed output maintains uniform structural patterns across different documentation sources and repository types.