docs-rewrite-all

Audit repository markdown files and propose rule-compliant rewrite diffs.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/hirokimry/vibecorp --skill docs-rewrite-all
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-rewrite-all
Source: https://github.com/hirokimry/vibecorp/tree/main/skills/docs-rewrite-all
Command: npx skills add https://github.com/hirokimry/vibecorp --skill docs-rewrite-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you systematically find and repair repository documentation that drifts from the project’s writing standards, without changing meaning by accident. It is designed for large markdown surfaces where consistency, scanability, and governance matter.

Core Features & Use Cases

  • Repository-wide audit: Scans docs/**/*.md, README.md, and CHANGELOG.md to find rewrite candidates.
  • Rule-based verification: Compares content against documentation, comment, communication, markdown, shell, and autonomy rules.
  • Delegated rewrite proposals: Routes each document domain to the right C*O role, then prepares file-level diffs for CEO review.
  • Approval-gated execution: Prevents automatic merging and only applies changes after explicit human approval.
  • Use case: Use it when a project’s docs need a coordinated cleanup that must stay faithful to existing meaning while becoming more compliant and readable.

Quick Start

Ask the assistant to audit the repository’s markdown files, propose compliant rewrites as diffs, and wait for CEO approval before applying any changes.

Frequently Asked Questions about docs-rewrite-all

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

FAQPage Schema
How do I rewrite markdown documentation across my repository without changing the original meaning?

To rewrite markdown documentation safely, audit README, CHANGELOG, and docs/**/*.md files against explicit writing rules, generate diff proposals, and require CEO approval before applying any changes to ensure meaning is preserved.

How does an approval-gated workflow help with repository documentation audits?

An approval-gated workflow prevents automatic merging during a documentation audit by routing proposed markdown rewrites to C*O roles and strictly requiring final CEO approval before any edits are applied to the repository.

What is the best way to enforce writing standards in markdown files?

The best way to enforce writing standards in markdown files is using mechanical rule matching to scan documentation, comments, and shell snippets, then generating file-level diffs for staged review instead of applying direct edits.

Can I automatically merge documentation rewrites after a repository audit?

No, you cannot automatically merge documentation rewrites. The process strictly refuses unapproved edits and requires explicit human CEO approval to apply any changes generated during the markdown audit.

When do I need delegated review for markdown documentation updates?

You need delegated review for markdown documentation updates when your project requires coordinated cleanup across large surfaces, routing each document domain to the appropriate C*O role before final CEO-approved changes are applied.