Create Draft Pull Request
Validate the current session’s changes and open a draft PR through GitHub MCP.
The skill restricts GitHub operations to the GitHub MCP server and asks for review of session changes, but it does not define permission scope, data flow, sensitive-data handling, user confirmation, final confirmation before commit/PR creation, or rollback. Committing changes, fixing arbitrary errors, and creating a remote draft PR can have durable external effects, so points are deducted. Microsoft provenance and the MIT license support attribution but do not replace missing safeguards.
The sequence is coherent and includes compilation, hygiene checks, change review, and PR creation. However, it omits concrete commands, failure handling, abnormal repository states, no-change behavior, and diagnostics when the MCP server is unavailable. “Fixing any errors” can also expand scope. Because this is a static review without executable reproduction evidence for this skill, the score is conservative and capped.
The name, description, and primary trigger are clear: create a draft PR from current session changes. Boundaries are incomplete because required inputs, target branch, remote state, permissions, non-fit scenarios, and Chinese-language interaction are unspecified. The core function depends on GitHub MCP, while network reachability and fallback behavior are not documented.
The front matter is concise and consistent with the capability, while repository-level README, MIT licensing, Microsoft attribution, and general maintenance context are available. The skill itself lacks installation/dependency notes, parameter contracts, examples, FAQs, known limitations, versioning, changelog, and an explicit maintenance/update path.
The workflow addresses the core task by checking the codebase, committing session changes, reviewing them, drafting PR metadata, and creating a draft PR. Points are deducted because output format, branch/base selection, the scope of automatic fixes, and acceptance criteria are unspecified, leaving meaningful manual review. Static inspection cannot verify successful completion, so the score stays within the static ceiling.
The instructions are directly auditable, and repository scripts and CI provide contextual evidence. There is no dedicated test, execution record, third-party run evidence, or MCP trace for create-draft-pr, and the supplied CI workflows do not cover its key path. Evidence therefore supports only limited verification.
- Require explicit user confirmation before committing changes or creating the draft PR, and disclose the target branch, remote repository, uploaded changes, and rollback method.
- “Run compile and hygiene tasks, fixing any errors” lacks concrete commands and repair boundaries and may authorize unintended code changes.
- Document GitHub MCP permissions, diagnosable behavior when the service or network is unavailable, and handling for no-change or failed-check cases.
What does this skill do, and when should you use it?
This skill creates a draft pull request for changes made in the current session. It first runs compile and hygiene tasks and fixes any errors found. If changes remain uncommitted, it uses the /commit skill to commit them. It then reviews the session’s changes, writes a concise area-prefixed title and a review-oriented description, and creates the draft PR through the GitHub MCP server.
Runs compile and hygiene tasks and fixes errors; checks for uncommitted changes and invokes the /commit skill when needed; reviews all changes in the current session; writes a PR title with a short area prefix; writes a description covering what changed, why it changed, and what reviewers should know; and creates a draft pull request through the GitHub MCP server. It explicitly prohibits use of the gh CLI.
- A developer has finished a session of code changes and wants a draft PR before merging.
- A contributor wants compilation and hygiene checks performed and errors addressed before opening a PR.
- A developer still has uncommitted workspace changes and needs them committed before creating the PR.
- A maintainer wants the PR title to include a short area prefix and the description to explain the change and review context.
What are this skill's strengths and limitations?
- Covers the workflow from compile and hygiene checks through draft PR creation.
- Requires review of all current-session changes and specifies the expected PR title and description content.
- Uses the GitHub MCP server explicitly instead of the gh CLI.
- The source does not provide concrete compile, hygiene, or MCP configuration commands.
- It depends on a GitHub MCP server, but authentication, required permissions, and recovery behavior are not documented.
- It is scoped to creating a draft PR for current-session changes and does not describe merge, release, or full PR management workflows.
How do you install this skill?
The repository bundles 61 skills, but the README provides no separate installation command. The skill is located at src/vs/sessions/skills/create-draft-pr/SKILL.md. Using it also requires an available GitHub MCP server and, when the session has uncommitted changes, the /commit skill.
How do you use this skill?
In an Agent Skills-compatible client with this skill loaded, make a request such as: “Create a draft PR for the current session’s changes.” The skill will run compile and hygiene tasks, commit changes when necessary, review the changes, write the title and description, and create the draft PR through GitHub MCP. The source does not specify the exact compile commands, hygiene commands, or GitHub MCP server configuration steps.
How does this skill compare with similar options?
Unlike the gh CLI, this skill explicitly requires the GitHub MCP server to create the draft PR and forbids use of the gh CLI. The source provides no further comparison of their features, permissions, or setup.