technical-writing

Use when writing, editing, or reviewing technical artifacts — READMEs, CONTRIBUTING and setup guides, knowledge-base pages, runbooks, migration and upgrade guides, API reference prose, architecture and design documents, release notes, long-form docstrings, pull request descriptions, or issue and ticket descriptions — including making text clearer for non-native English readers. Do not use to review README or documentation files the user changed in this checkout; engineering:review-changes owns that review and applies this skill inside. Do not use to assess, triage, or decide changes from unresolved review feedback. Once another workflow settles the feedback, use for drafting or rewriting technical comments in issue trackers, pull or merge request comments, and reviewer replies. Do not use for decision records (engineering:decision-records); for agent-instruction files such as AGENTS.md or SKILL.md; for chat responses, commit messages, or code comments; or for conceptual questions about writing standards.

License

MIT