Write enough to preserve the contract, then remove reasoning transcripts, repetition, and decoration. A contract is an obligation, invariant, precondition, postcondition, or compatibility promise that a caller, callee, implementer, producer, consumer, reader, or maintainer relies on. This skill owns editorial judgment and required prose coverage; follow your repository's documentation standard for placement, budgets, bilingual pairs, and documentation gates, and audit reasoning-transcript leakage — dead session citations, change narration, review choreography, hedges — with its own taxonomy. It is guidance, not a script.

Treat , , , , , , and as terms to check before use, not banned words. First ask whether the exact rule, API, field set, type, validation, timing point, component split, or failure states the fact better. Keep a term when it names the exact technical subject, including caller/callee contracts and security or process boundaries.

Require an explicit . If it is missing, report the required input and stop; do not infer a repository-wide scope or begin an interview.

Accept ; default to . Enter interactive mode only when the user explicitly requests questions or calibration. controls questions, not write authority: review and audit tasks report findings without editing; explicitly requested write, fix, or trim tasks apply clear changes.

Always exclude from discovery, review, and edits, even when the requested scope is the whole repository. Do not follow a symlink into it. Put exclusions after inclusion globs so a later include cannot re-admit it — for example, end ripgrep commands with and give Git commands an explicit pathspec. If the requested scope contains only , report that no eligible files remain.

Also exclude frozen archived notes from review and edits. Archived notes are frozen snapshots; inspect an exact target only to understand a historical inbound citation, never to modernize its prose or outbound links.

Treat generated catalogs, snapshots, and fixtures as derivative. Edit the owning source or scenario first, then regenerate the artifact. When a generator extracts a summary from owner prose, make the extracted sentence complete for that surface. Bilingual pairs have no permanent owner: either language may be the authored side for an update, and the counterpart must follow in the same change.

Before editing, identify every proposition in the passage. Preserve each relevant:

Remove adjectives, repetition, and narration only when every factual clause survives and the result is clearer. A smaller word count alone is not an improvement.

Keep a complete local contract at the point of use: behavior, failure, ownership, and consequence that a caller or maintainer needs there. Aggressively link to the owning document for architecture, rationale, algorithms, history, or extended examples. One explanation has one home; essential contract facts may repeat locally. Keep non-obvious rationale when omitting it could plausibly cause misuse or an incorrect simplification; otherwise state the consequence and link the rationale home.

Comments describe non-obvious contracts or rationale that code cannot express; they do not restate what code already implies. This is not a one-way shortening pass: add or restore prose when code, types, and structure do not communicate a required contract, and do not add a comment when those facts are already obvious locally.

Required coverage spans skill bodies and descriptions, instruction files, READMEs, Agent Notes, JSDoc, internal and module comments, tests, cookbooks, postmortems, configuration comments, prompts and visible strings, and diagnostics. The full per-location list lives in the coverage reference. Preserve searchable mechanism names and meaningful modal, temporal, or negative emphasis; normalize decorative emphasis only.

A case is borderline only when at least two versions satisfy the complete-proposition rule but trade accepted principles, and this skill does not already resolve the tradeoff. A rewrite with one proposition-preserving answer is not borderline.

In automatic mode, apply clear edits when authorized and report genuine borderline cases without asking questions. Do not weaken a proposition to make progress.

In interactive mode, group analogous passages under the governing principle. Present two or three viable versions, recommend one, and state the factual or structural difference. Do not offer inferior distractors. Use the user's requested channel; when calibrating a change through inline comments, place the recommended provisional version in the diff and attach the alternatives to that exact line.

After the user decides, distill the principle and versions into the examples, without review history or reviewer narration, and apply the learned rule to every analogous passage in scope.