Write PR

Defaults

• Write in English unless the user requests another language.
• When asked to open a PR, create it ready for review. Use draft only when explicitly requested. Writing wording alone does not authorize pushing, opening, or updating a PR.
• Use local domain names and required repository fields. Keep the user's language and ready/draft preferences rather than inheriting a conflicting template default; omit empty boilerplate.

Understand, then select

Read the actual diff and enough context to understand the change. Describe the current PR's contribution, using an earlier PR link for shared stack context. Rewrite around the final implementation when scope changes.

For stacked delivery, follow the stack checks below before creating a PR.