Create PR

Write for busy developers: make the change and its purpose clear before adding detail.

Read the current template

Find and read the repository's applicable PR template every time, including HTML comments, linked guidelines, and contribution instructions. Check the repository root, .github/, and docs/, including template directories. If several templates exist, choose the one that fits the change.
Use the template's current sections, order, length limits, and checklist instructions. Do not copy its structure into this skill or reuse a remembered version.
Prefer the actual current PR template over stale copies of its structure in other guidance; still follow any compatible contribution rules.
If no local template exists, check the target repository and its shared GitHub defaults. If none exists, use a compact structure suited to the change and say that no template was found.
Inspect the full diff against the intended base branch and the relevant issue context. Describe the final change, not the sequence of work or abandoned approaches.

Fit the following content into the template's appropriate sections rather than adding a fixed set of headings: