prlisted

# Pull Request Create pull requests with proper templates and metadata. ## Requirements - PR should use the PR template of the current repository - Assignee is automatically set by CI (random CODEOWNER) - Labels are automatically applied by CI based on changed files ## Issue Detection If the branch name contains an issue number (e.g., `feat/123-add-feature`, `fix/45-parser-crash`), extract it and fetch the issue details: ```bash gh issue view <number> --json title,body,labels ``` Use the issue context to: 1. Link the issue using the **Closes** section format (see below) 2. Inform the PR summary and description from the issue's title and body If no issue number is found in the branch name, skip this step. ## Issue Link Format **Always** use this exact format when linking issues in a PR body. Replace the repo's `## Related Issues` template section with a `## Closes` section: ```markdown ## Closes - Closes #123 - Closes #456 - Relates to #789 ``` This format ensures GitHub renders rich issue links (with title, status, etc.) automatically. Do **not** append the issue title after the number — GitHub handles that via its rich formatting. Rules: - Use a `## Closes` heading (not `## Related Issues`) - Each link is a bullet point: `- Closes #<number>` - Use `Relates to` instead of `Closes` for issues that are related but not fully resolved by this PR - Do **not** add any text after the issue number (no titles, no descriptions) ## Usage When asked to create a PR: 1