Session Pull Request Assistant
Checks session changes and creates a GitHub pull request through GitHub MCP.
The skill explicitly requires GitHub MCP instead of the gh CLI and asks for change review before PR creation. However, it allows fixing errors, committing uncommitted changes, and creating a PR without an explicit user confirmation step, while omitting permission scope, data-flow disclosure, sensitive-data handling, rollback, and revocation guidance; points are deducted for these gaps.
The sequence is internally coherent and covers compilation, hygiene, review, committing, and PR creation. However, it does not name exact commands, define failure handling, provide abnormal-input feedback, verify GitHub MCP availability, or explain how to stop safely when fixes are uncertain; static evidence also prevents a score above 10.
The name, description, and trigger are clear for users who want a pull request created from current session changes. Boundaries are under-specified for branch state, remote state, permissions, and non-applicable cases, with no Chinese-language guidance; the core GitHub MCP dependency may also be difficult to reach from mainland-China networks.
The front matter is concise and naming is stable, while the README, MIT license, and Microsoft maintenance context provide partial provenance and governance evidence. The skill lacks installation/dependency notes, parameter definitions, examples, FAQs, limitations, versioning, changelog, and a skill-specific maintenance path, so points are deducted.
The workflow addresses the core path from checking changes to submitting a pull request and requests a concise prefixed title plus a useful description. It does not define the exact compile or hygiene scope, ensure complete intended changes, or verify the created PR, leaving meaningful manual review and limiting the static score to 7 or below.
The instructions are auditable, and package.json exposes compile, hygiene, and test scripts that support parts of the workflow; README and license provide source and governance evidence. There is no skill-specific test suite, CI coverage, or reproducible evidence for PR creation, and this review is static only, so the score remains low.
- Creating a PR and committing local changes are external and durable actions; explicit confirmation of the target branch, commit contents, PR metadata, and permission scope should precede them, with recovery guidance for failures.
- GitHub MCP is a core dependency, but installation, authentication, permission requirements, and diagnostics when unavailable are undocumented; mainland-China network reachability may affect use.
- “Compile and hygiene tasks” lacks exact commands and success criteria, which may cause inconsistent scope and unnecessary modifications.
What it does & when to use it
This skill creates a GitHub pull request for changes made in the current session. It first runs compilation and hygiene tasks, fixing any errors it finds. If uncommitted changes remain, it invokes the /commit skill, then reviews all changes from the session. It finishes by generating an area-prefixed title and a reviewer-oriented description before creating the pull request through GitHub MCP without opening a confirmation UI.
Runs compilation and hygiene tasks; invokes the /commit skill when uncommitted changes exist; reviews all current-session changes; writes a concise pull request title with a short area prefix; writes a description covering what changed, why, and reviewer-relevant information; creates the pull request through GitHub MCP with show_ui=false.
- A developer has finished a set of session changes and wants the validation and pull-request workflow handled together.
- A contributor wants compilation, hygiene checks, and change review completed before opening a pull request.
- A team member needs to create a pull request through GitHub MCP instead of the gh CLI.
- A maintainer wants a concise title and description that explain the change and its rationale to reviewers.
Pros & cons
- Covers validation, committing, review, and pull-request creation in one workflow.
- Explicitly uses GitHub MCP rather than the gh CLI.
- Requires an area-prefixed title and a description explaining the change, rationale, and reviewer considerations.
- The repository is licensed under MIT.
- The source does not specify the exact compilation or hygiene commands.
- It depends on a GitHub MCP server and the /commit skill.
- No skill-specific test suite or detailed failure-handling procedure is provided in the source.
- The skill is scoped to current-session changes and does not explain handling for other branches or cross-session changes.
How to install
The skill is located at src/vs/sessions/skills/create-pr/SKILL.md in the microsoft/vscode repository. The README describes it as part of a bundled collection of 61 skills, but does not document a standalone installation command or destination folder.
How to use
In an environment containing the current session's changes, make a request such as: “Create a pull request for the current session's changes.” A GitHub MCP server must be available; the skill then performs the checks, handles commits, reviews the changes, and creates the pull request.
Compared to similar skills
The source explicitly names the gh CLI as an alternative and directs users to use GitHub MCP instead. It does not provide enough information for further tool comparisons.