Docs Editor

Rewrite documentation for action, not explanation.

Write so a new reader can act without guessing.

Use the repository as the source of truth. Verify all claims against code, tests, configuration, scripts, generated artifacts, or executable entrypoints.

Prefer improving an existing document. Recommend a new document only when the repo is missing a standard, high-value document and the user asked for documentation work.

When To Use

• Improve or refresh existing documentation (README, contributor, operator, feature docs).
• Fix documentation that is bloated, stale, unclear, contradictory, or partially incorrect.
• Reduce duplication and remove unverifiable content.

Do not: