Applying PR Conventions

Compose five values for one pull request and return them: the title, the body, the ai-review label choice, the resolved t: label that the title's type keyword maps to, and which template the body came from. Returning to the caller defines that last one; do not restate its possible answers anywhere else in this file.

The caller says how many pull requests it is composing for and whether any value is already settled. Follow its instruction over the defaults below.

Step 1 — Title

[<TICKET>] <type>: <short imperative summary>

• Invoke Skill(labeling-changes) to pick the <type> keyword and the t: label it maps to. CI reads the keyword to apply the label.
• Include the ticket key when the branch name or the conversation has one, or when the caller supplies it. Bitwarden does not require a ticket on every pull request, so drop the bracket entirely rather than inventing a key or leaving a placeholder.
• Show the proposed title to the user.
• Return the t: label the keyword maps to, alongside the title.

Step 2 — Body