pr-creation_skill

Overview

This skill helps you create, open, or edit GitHub pull requests following team best practices. It detects associated ticket numbers, applies PR templates when present, and creates PRs as drafts by default to avoid premature review notifications. The goal is consistent, traceable PRs with clear titles and formatted descriptions.

How this skill works

The skill inspects conversation context, current branch name, and recent commit messages to detect ticket identifiers (Jira or GitHub issues). It searches the repository for PR templates in .github/, fills template fields (including ticket placeholders), constructs a ticket-prefixed title and a well-structured body, and runs gh pr create --draft with a heredoc body. It verifies creation, returns the PR URL, and reminds the user how to mark the PR ready for review.

When to use it

• When the user asks to create, open, submit, raise, file, or make a PR
• When you want the PR to include a ticket reference automatically
• When a repository contains a PR template that should be respected
• When you prefer creating a draft PR to run CI before requesting reviews
• When preparing a PR from a branch or recent commits and need a standardized description

Best practices

• Always attempt to detect a ticket from conversation, branch name, or commits before asking the user
• Search .github/ for pull request templates and preserve template structure when filling fields
• Format titles as [TICKET] Descriptive title when a ticket is found
• Create PRs as drafts using --draft to prevent premature reviewer notifications
• Include ticket links when a ticket URL can be determined; otherwise include the ticket number

Example use cases

• Create a draft PR from branch MSI-608/zendesk2, include [MSI-608] in the title and fill the template’s ticket field
• Open a PR when branch name contains an issue number like 456-fix-auth-bug and link to the GitHub issue
• Generate a PR body from recent commits when no template exists, adding summary, changes, and test plan
• Ask which template to use if multiple templates exist in .github/PULL_REQUEST_TEMPLATE/
• Prompt the user to select the primary ticket when multiple ticket references are detected