pr-description-skill

# PR Description Skill -- Anchored, Concise, Validated PR Bodies ## When to use Trigger this skill on any of the following intents: - "write a PR description" - "draft a PR body" - "open a PR" / "open this PR" / "let's open the PR" - "fill in the PR template" - "summarize this branch as a PR" - "create the PR write-up" Reusable for any PR against `microsoft/apm`. The output is one markdown file that the orchestrator pastes into `gh pr create --body-file` or surfaces to the maintainer. ## Output charset rule (read this first) The repo-wide encoding rule at `.github/instructions/encoding.instructions.md` constrains **source files and CLI output** to printable ASCII because Windows cp1252 terminals raise `UnicodeEncodeError` on anything else. PR comments are NOT source code and NOT CLI output -- they are rendered by GitHub's Primer engine, which expects UTF-8 GitHub-Flavored Markdown. Two distinct rules therefore apply: 1. **Source files in this bundle** (`SKILL.md`, `assets/*`) MUST stay ASCII. They live in the repo and are subject to `.github/instructions/encoding.instructions.md`. 2. **The PR body output the skill produces** MUST be UTF-8 GitHub-Flavored Markdown. Use em dashes, smart punctuation, alerts, collapsibles, task lists, and Unicode where it improves readability. Mermaid diagram labels MAY use Unicode -- there is no constraint here. The output is consumed by GitHub's renderer, not by a Windows terminal. A previous version of this skill ...