Pull Request Guidelines

Use This For

Use this skill to write or review PR titles, PR descriptions, changelog entries, issue closing language, GitHub username verification, reviewer guidance, and merge strategy.

If the task is only staging, splitting, or committing local changes, use git. If the task is issue triage or public issue replies, use github-issues.

Hard Rules

• Write PR descriptions as continuous narrative prose, opening with WHY.
• Never include ## Summary, ## Changes, ## Testing, ## Test Plan, or ## Verification sections unless the user explicitly asks.
• Report commands run, tests run, and verification gaps in the chat final response, not the PR body.
• Do not list changed files. The diff tab already does that.
• Do not include AI or tool attribution.
• Add a ## Changelog section only for feat: and fix: PRs with user-visible changes.

References