oss-writinglisted

# Repo prose Write with clarity and force for a reader whose first language is not English. Be terse. This skill owns how the sentence reads. The skill that owns the artifact owns what goes in it, and where a caller states an exception, the caller wins. ## Limited context strategy When context is tight: 1. Write your draft using judgment 2. Copyedit the draft against the reference for that artifact, with only those two in context 3. Ship the revision, not the draft ## Read the local contract first Before drafting, read the repository's instructions, contribution guide, templates, and the most recent accepted examples of the same artifact. They decide the commit convention, the required sections, the terminology, and the audience. Follow the convention the repository declares rather than inventing one, and keep required template sections and legally mandated wording. Verify every claim against the diff, the source, or command output. Prose that reads well and says something untrue is the one failure no rule below catches. ## Core rules (all artifacts) - Form the possessive singular by adding 's. - Enclose parenthetic expressions between commas. - Put a comma before the conjunction introducing a co-ordinate clause. - Do not join independent clauses by a comma. - Do not break sentences in two. - Make a participial phrase at the beginning refer to the grammatical subject. - Use active voice. Name who acts. - Use the imperative or present tense. Avoid complex tenses. - S