dhughes/claude-marketplace
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
FAQ
I will ask whether a ticket should be associated; if the user declines, I will proceed without a ticket in title or body.
What if the repository has no PR template?
I will generate a comprehensive PR description with summary, changes, and test plan and include the ticket (if any) at the top.
Will the PR be ready for review immediately?
No. The skill creates draft PRs by default. You can mark a draft ready with gh pr ready <pr-number> or using the GitHub web UI.
9 skills
This skill creates draft pull requests by automatically detecting related tickets, applying templates, and including ticket references for easy review.
This skill establishes test-driven development requirements before feature work, ensuring explicit test plans and early test-driven implementation.
This skill guides you in using the atl CLI to interact with Jira and Confluence, extracting IDs from URLs and running commands.
This skill loads a past Claude conversation by UUID into the current context, enabling seamless reference and context restoration.
This skill helps you investigate ezCater systems and project histories across Glean, Jira, Confluence, and Git to reveal architectural decisions.
This skill monitors GitHub PR CI checks until completion and notifies you of the final result, ensuring you never miss failures.
This skill guides you through initial setup and indexing of conversation history to ensure past conversations become searchable.
This skill helps you manage statusline components globally or per project by discovering, listing, and configuring enabled items.
This skill monitors Google Cloud Build using the gcloud CLI and provides continuous status updates with actionable failure analysis.
