name	pull-request
description	Creates concise GitHub pull requests with Conventional Commit titles and issue-closing references. Use when asked to open a pull request.

Pull Request

Use a short Conventional Commit title. Do not add an issue number to the title unless the repository requires it. In this repository, classify skill-file changes as feat or fix, never docs.
Write one high-level plain-English paragraph for the body. Leave out implementation details, test logs, file lists, checklists, and review notes unless a repository template requires them.
When the PR resolves a GitHub issue, include Closes #<issue-number> in the body. Use Fixes #<issue-number> only when that wording better matches the work. Do not mention issues the PR does not resolve.
After creating the PR, verify the title and body. If a required issue-closing reference is missing, update the PR body immediately.

name	pull-request
description	Creates concise GitHub pull requests with Conventional Commit titles and issue-closing references. Use when asked to open a pull request.

Use a short Conventional Commit title. Do not add an issue number to the title unless the repository requires it. In this repository, classify skill-file changes as feat or fix, never docs.
Write one high-level plain-English paragraph for the body. Leave out implementation details, test logs, file lists, checklists, and review notes unless a repository template requires them.
When the PR resolves a GitHub issue, include Closes #<issue-number> in the body. Use Fixes #<issue-number> only when that wording better matches the work. Do not mention issues the PR does not resolve.
After creating the PR, verify the title and body. If a required issue-closing reference is missing, update the PR body immediately.

pull-request