<< All versions
Skill v1.0.2
currentAutomated scan100/100benmatselby/dotfiles/draft-pr
~1 modified
──Details
PublishedNovember 4, 2026 at 04:30 PM
Content Hashsha256:2ce8c619b407c719...
Git SHA35d2e12fcc30
Bump Typepatch
──Files
Files (1 file, 1.8 KB)
SKILL.md1.8 KBactive
SKILL.md · 42 lines · 1.8 KB
name: bms:draft-pr description: Create a draft pull request for the current branch. Summarises the diff, fills in any PR templates, and opens the PR via the gh CLI. metadata: version: "1.0.2"
Draft Pull Request
Create a draft pull request for the current branch with a well-written _and concise_ summary.
- Confirm the current branch is not
main. If it is, create a relevant branch name first. - Identify the base branch.
- Confirm there's at least one commit ahead of it:
git log <base>..HEAD --oneline. If empty, stop and tell the user. - Warn the user if there are uncommitted changes in the working tree - the PR should represent the committed state.
- Gather context using
git logandgit diff. - Understand the full diff carefully. Understand what changed and why.
- Check for a PR template.
- Check, in order:
.github/pull_request_template.md,.github/PULL_REQUEST_TEMPLATE.md,docs/pull_request_template.md,pull_request_template.md,.github/PULL_REQUEST_TEMPLATE/*.md. - If found, fill in every section based on the diff - never leave one empty (write "N/A" with a reason if not applicable).
- If not found, use the following format: "Summary", "Changes", and "Notes" (if applicable).
- Do not do both!
- The title should be concise, imperative mood ("Add user authentication", not "Added..."), under 72 characters.
- Check if conventional commits are used, if so, follow that convention for the title.
- Please make it clear on the PR what the full prompts were (if any), with any questions answered. The format should be:
🤖 AI promptsPrompt 1> The prompt usedPrompt 2 etc> The pronmpt used
- Raise the PR in draft mode using the
ghCLI. - Request that Copilot for a review.
- Give the user the PR URL and confirm the title and draft status.