Use this skill to write the PR description (PR body) for any pull request opened against microsoft/apm. Produces one self-sufficient GitHub-Flavored Markdown artifact: TL;DR, Problem (WHY), Approach (WHAT), Implementation (HOW), 1-3 validated mermaid diagrams, explicit trade-offs, validation evidence, and a How-to-test section -- with every WHY-claim backed by a verbatim quote from PROSE or Agent Skills. Activate when the user asks to "write a PR description", "draft a PR body", "open a PR", "fi
SkillScore86Maintained
Automatic
◆Coding pack
Last verified 8/7/2026
What it changes
Passed 17 of 20 test cases with the skill, and 7 of 20 without it.
Without skill36%
With skill86%
Checks it passed that the model alone missed
Limits the How to test section to a maximum of 5 steps.
Requires validating Mermaid blocks using mmdc before saving the draft.
States that repository source files must remain strict printable ASCII.
and 8 more in the full report
11 fixed8 passed either way3 still failing0 broke
Pass-rate lift
+50 pp
Tokens
+213%
Agent turns
0%
Response time
-51%
Model gemini-3.6-flashMeasured 8/7/2026v119 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
Write a short git commit message for my local change fixing a typo in README.md.
What was checked, without and with the skill
Checked
Without skill
With skill
Formats the commit message header using the Conventional Commits type `docs: fix typo in README.md`.
Missed
Passed
case-20 · gemini-3.6-flash · 8/7/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
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:
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.
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 incorrectly required ASCII in the