// Generate a PR title and description from the current branch diff against main
Manage local multigres cluster components (multipooler, pgctld, multiorch, multigateway) - start/stop services, view logs, connect with psql, test S3 backups locally
Run unit tests, integration tests, and development tasks for multigres
Fix markdown linting and prettier formatting issues in markdown files
| name | draft-pr |
| description | Generate a PR title and description from the current branch diff against main |
| disable-model-invocation | true |
Generates a PR title and description based on the diff between the current branch and upstream/main, and creates a draft PR.
/draft-pr
When this skill is invoked, follow these steps:
Run these commands to understand the changes:
# Get the branch name
git branch --show-current
# Get the commit log for this branch (commits not on main)
git log --oneline upstream/main..HEAD
# Get the full diff against main
git diff upstream/main...HEAD
If the diff is large, also run git diff --stat upstream/main...HEAD first for an overview, then read specific files as needed.
Compose the title and body following this structure:
Title: <type>(<scope>): <short description>
Body:
## Summary
<2-4 bullet points describing what changed and why>
Then choose the appropriate detail sections based on the nature of the PR:
If the PR fixes a bug or addresses a non-obvious issue, add:
## Problem
<Brief description of the issue being solved>
## Solution
<Brief description of the approach taken>
Otherwise (pure feature, refactor, or when summary alone isn't enough), add:
## Description
<More detailed explanation of the changes, covering the what and why>
If the summary already says everything, you can omit the extra section entirely.
Push the branch to the remote if not already pushed, then create a draft PR:
# Push the branch (set upstream if needed)
git push -u origin HEAD
# Create draft PR using the generated title and body
gh pr create --draft --title "<title>" --body "<body>"
Use a HEREDOC for the body to preserve formatting:
gh pr create --draft --title "<title>" --body "$(cat <<'EOF'
<body content here>
EOF
)"
Print the PR URL when done so the user can review it.
feat, fix, docs, test, refactor, chore, build, ci, perf. Keep it under 72 characters.<br>), so wrapping at ~70–80 chars produces visible broken-up sentences in the rendered PR.