con un clic
pr-create
// Create a GitHub pull request as a draft, auto-generating title and body from commits
// Create a GitHub pull request as a draft, auto-generating title and body from commits
Create a commit (or draft a commit message) in a Git repository
Create a commit (or draft a commit message) in a Jujutsu repository
How to use `jj`, the Jujutsu version control system
Review a GitHub pull request, examining the summary, linked resources, and diff
Interact with Neovim via RPC to annotate code, navigate files, and do walkthroughs
This skill should be used when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.
| name | pr-create |
| description | Create a GitHub pull request as a draft, auto-generating title and body from commits |
| allowed-tools | ["Bash","Read","Glob","Grep","AskUserQuestion"] |
Create a GitHub pull request for the current branch using the gh CLI.
Determine the default branch by running:
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'
Use this as the base branch unless the user has specified a different base.
Gather context by running these in parallel:
git log <base>..HEAD --oneline to see all commits being proposedgit diff <base>...HEAD --stat to see a summary of changed filesgit diff <base>...HEAD to see the full diffCheck for a PR template by looking for files in these locations (in order of priority):
.github/PULL_REQUEST_TEMPLATE.md.github/PULL_REQUEST_TEMPLATE/ directory (if multiple templates exist,
pick the default one, or ask the user which to use)PULL_REQUEST_TEMPLATE.md (repo root)If a template is found, read it and use its structure for the PR body. Fill in the template sections based on the commits and diff.
Draft the PR title and body:
Present the draft to the user:
Create the PR by running:
gh pr create --draft --title "<title>" --body "<body>" --base <base-branch>
Use a HEREDOC for the body to preserve formatting.
Report the PR URL back to the user.
git push -u origin HEAD (after checking that origin is the correct remote
for GitHub by inspecting the output of git remote -v).