create-pull-request Skill
Create a GitHub Pull Request from the current or specified branch. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes to a repository. Published by microsoft in vscode-pull-request-github.
Decision snapshot
Is this a fit?
Developers using vscode-pull-request-github, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is create-pull-request Skill?
Create a GitHub Pull Request from the current or specified branch. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes to a repository. Published by microsoft in vscode-pull-request-github. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using vscode-pull-request-github
Declared skill metadata
- Source file: src/lm/skills/create-pull-request/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use create-pull-request Skill
- Use it for developers using vscode-pull-request-github.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-pull-request-github
- Skill file: src/lm/skills/create-pull-request/SKILL.md
What it does
Create a GitHub Pull Request from the current or specified branch. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes to a repository.
Skill instructions
Create a GitHub Pull Request Gather the necessary information, prepare a clear title and description, then call the tool to open the pull request. When to Use - The user wants to open a PR for their current or a specified branch - The user has finished a feature or fix and wants to submit it for review - The user wants to create a draft PR to share work in progress - The user asks to "open a PR", "create a pull request", or "submit for review" Procedure 1. Gather Information Determine the required parameters before calling the tool: - Head branch: If the user has not specified a branch, use workspace or git context to find the current branch name. Do not use owner:branch format - pass just the branch name (e.g. my-feature). - Base branch: If the user has not specified a base branch, omit it and let the tool use the repository's default branch. - Title: If the user has not provided a title, derive one from the branch name, recent commits, or the user's description of their work (see Bes
Verified compatibility and discovery
Frequently asked questions
What is create-pull-request?
create-pull-request is a open-source AI agent skill with Copy skill directory. Create a GitHub Pull Request from the current or specified branch. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes to.
Who is create-pull-request best for?
create-pull-request is best for reusing agent instructions, scripts, and references.
How do I install create-pull-request?
Install or run create-pull-request using Copy skill directory. Check create-pull-request for the latest setup command.
Is create-pull-request actively maintained?
create-pull-request may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
