comment-policy

# Comment policy (FR-22 write-time carrier) > **Style:** Mode-B-lite. The write-time home of FR-22. Loads for code-writing agents (and their sub-agents) so the rule reaches the writer's context at the moment comments are written — not just at review. Rule body aligns with FR-22 in `FLOW_RULES.md`; rationale + evidence live in `docs/comment-policy.md`. ## Purpose Flow source is read by AI agents, not humans line-by-line. WHAT-restating prose, rationale already homed in a decision/ticket/memory, and changelog comments serve an absent audience and cost context budget on every load. The base "match surrounding comment density" instruction is a one-directional ratchet and every Stop-hook gate is comment-blind, so over-commenting is invisible to the loop. This skill delivers the explicit override at write time. ## When to invoke - Writing or editing code in any language. - Adding, changing, or reviewing your own comments before a commit. - About to commit a code diff (final comment pass). - A handoff or task involves implementation, refactor, or scaffold. ## Do not invoke when - Editing prose / docs / specs / decisions / handoffs (these are human-or-AI-read narrative, not code). - The ticket is non-code (config-only rename, doc-only change with no source edit). - You want review-time enforcement — that is `code-review` (the review dimension), not this write-time carrier. ## Required inputs | Input | Where it lives | If missing | |---|---|---| | The code diff being written ...