Reply and Review Discipline

Someone else's thread: the reader skims it and does not know the code, and whatever is written there publishes under the user's name. Plain words first, the reader's own log lines with arrow notes, questions only when the report does not answer them, and on a PR one pending review the user publishes.

These rules apply to any session writing on a thread it does not own: an issue reply, or a review of someone else's PR. The user's own PR or issue is the /pr-and-issue-discipline skill's moment. Its Readability rules and its redaction rule apply here unchanged; they are stated there, once.

/unslop, where installed, runs last over every reply and staged comment: it publishes under the user's name, so no AI tells.

When to Apply

• Replying to an issue reporter or outside contributor
• Reviewing someone else's PR under the user's account

Replies to Issue Reporters: Plain First

An issue reply to an outside contributor is read by someone skimming a thread who does not know the code. Write a plain-language part that stands alone. Add a technical part, collapsed so it costs nothing to skip, only when it carries information the plain part cannot: when everything fits in plain words, the plain part is the whole reply.

A finding comment staged on someone else's PR follows the Each comment rules below and borrows only this section's voice; the staged summary has its own shape there.