pull-request

name	pull-request
description	Defines how pull requests must be formatted for this project. Use this skill whenever creating a pull request.

When creating a pull request, follow this format exactly.

---

Title

If a semver version bump was made as part of this PR, lead the title with the new version number in parentheses:

(0.2.1) Short description of the change

If no semver version bump was made, omit the version prefix entirely:

Short description of the change

The title must be:

• Under 70 characters, excluding the version prefix
• Written in sentence case
• Focused on what changed from the user's perspective, not how it was implemented

---

Body

Requirements reference

If a requirements GUID was provided (from a product/ file), include it as the first line of the body:

**Requirements:** `<guid>`

Omit this line entirely if no GUID is available.

---

Changes

Include a table summarising the behavioural changes in this PR.

If this PR was created using the new-feature skill, this table must contain exactly the information that was confirmed with the user before the technical specification was written — that is, the clarified feature requirements from the orchestrating session, not the internal technical spec.

If the PR was not created using the new-feature skill, provide a best-effort summary of the observable changes.

#	Area	Change
1	[component or user-facing area]	[what changed, described in terms of observable behaviour]

Test plan

Only include this section if manual testing is required. If all changes are covered by automated tests — as they will be when using the new-feature workflow — omit this section entirely.

If manual testing is required, list the specific steps a reviewer must take to verify the changes work correctly.

---

Rules

• Do not include a line stating the PR was generated by Claude or Claude Code.
• Do not include marketing language, filler phrases, or internal implementation details — focus on observable, user-facing behaviour.
• Do not include a test plan section unless manual testing is genuinely required.
• Do not pad the body with sections that have nothing to say.