doc-optimizer

Scan repository documentation for issues and apply safe auto-fixes.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/jasonmichaelbell78-creator/framework --skill doc-optimizer-jasonmichaelbell78-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-optimizer
Source: https://github.com/jasonmichaelbell78-creator/framework/tree/main/.claude/skills/doc-optimizer
Command: npx skills add https://github.com/jasonmichaelbell78-creator/framework --skill doc-optimizer-jasonmichaelbell78-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation quality drifts, leading to confusion, onboarding friction, and maintenance overhead across large repos.

Core Features & Use Cases

  • Auto-fix formatting, header metadata, and cross-link issues across docs.
  • Generate structured JSONL findings and enhancement recommendations for teams.
  • Provide a guided workflow to improve documentation quality over time.

Quick Start

Invoke the doc-optimizer to start the multi-wave analysis and automatic remediation.

Frequently Asked Questions about doc-optimizer

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

FAQPage Schema
How do I automate documentation formatting and link validation in my repository?

To automate documentation formatting and link validation, you need a tool that scans all non-archived docs to discover issues and applies safe auto-fixes. It operates using wave-based orchestration to plan remediation across headers, links, and cross-references.

What is the best way to fix broken cross-references and header metadata in project docs?

The best way to fix broken cross-references and header metadata is to run an automated documentation enhancement tool. It scans the repository, identifies formatting and link issues, and automatically remediates them while generating a unified governance report.

How does automated documentation linting generate actionable enhancement recommendations?

Automated documentation linting generates enhancement recommendations by scanning for issues across all non-archived docs, applying safe auto-fixes, and outputting structured JSONL findings. These findings provide teams with actionable insights to improve documentation quality over time.

Can I use automated doc validation across all non-archived files in a large repository?

Yes, you can use automated doc validation across all non-archived files in a large repository. The tool scans headers, links, and cross-references globally, applying safe auto-fixes and generating structured JSONL findings to handle maintenance overhead at scale.

How do I get structured JSONL findings for documentation governance and remediation?

To get structured JSONL findings for documentation governance, run an automated doc health scan. The process outputs JSONL findings and a unified report to a state directory, enabling teams to track remediation and improve documentation quality systematically.