[fredericoo]

TL;DR: The PR template and the repo's pull-request-standards skill describe two different shapes for a PR description. Agents follow the skill and humans follow the template, so descriptions are inconsistent. This makes the template match the skill, so there is one source of truth.

Before

WHY / WHAT / HOW to test headings, a post-merge section, and a five-item contributor checklist.

After

The skill's structure: a closing issue line and a TL;DR, followed by optional Before, After, What this changes, Developer impact, UX impact, Out of scope, Risk, and How to Test sections. Each section has a short comment that says when to use it and when to delete it.

What this changes

• Rewrites .github/PULL_REQUEST_TEMPLATE.md to follow skills/pull-request-standards.
• Moves the changeset guidance (patch / minor / major) into Developer impact, matching the skill's versioning rules.
• Moves the cross-platform reminder into Risk.
• Keeps the gif accessibility guidance (under UX impact) and Post-merge steps with the includes-post-merge-steps label. The skill doesn't cover either, but both are existing repo conventions.
• Removes the checklist. Its items are now covered by section prompts. Tests no longer have a checkbox, because the skill keeps automated tests out of PR descriptions.

Risk

• Without the checklist, nothing explicitly prompts for a link to the contributing guidelines or for added tests. If reviewers rely on those checkboxes, we can add them back as a short checklist.

[shopify]

Oxygen deployed a preview of your fb-pr-template-style branch. Details:

Storefront	Status	Preview link	Deployment details	Last update (UTC)
Skeleton (skeleton.hydrogen.shop)	✅ Successful (Logs)	Preview deployment	Inspect deployment	October 27, 2026 3:15 PM

Learn more about Hydrogen's GitHub integration.

[fredericoo]

superceded by #4210