REPO PACKAGE
microsoft vscode-pull-request-github
OFFICIAL7skills
6ready to use
LABSCO SUMMARY
The six general-purpose skills cover a PR's whole lifecycle from inside the editor: create-pull-request opens one from the current or a specified branch; address-pr-comments responds to review feedback, including Copilot's own review comments, and resolves the threads; form-github-search-query turns a natural-language request into a working GitHub search query for issues or PRs; show-github-search-result renders those results as a markdown table; and summarize-github-issue-pr-notification and suggest-fix-issue read an issue, PR, or notification and, respectively, summarize it or propose a fix. All six assume the Microsoft GitHub Pull Requests and Issues extension is already installed, signed in to GitHub, and pointed at a repository through its githubPullRequests.remotes setting.
This is a package for developers who already work through that extension day to day and want their agent drafting PRs, forming search queries, and acting on review comments through it rather than through raw gh calls. It gives no fallback for someone driving GitHub purely from a terminal or a different editor's extension — every one of the seven skill descriptions is written in the extension's own vocabulary of "the active pull request" and "the current branch", not a general GitHub API surface.
READ THE FULL ANALYSIS
write-changelog is the odd one out. It writes a CHANGELOG.md entry for a new extension release and requires a milestone name and a version number — the vocabulary of this repository's own release process, not something a reader's unrelated project has a use for. Someone installing this package for the other six skills will find the seventh useful only if they are releasing this exact extension.
One of the seven is unverified. The dependency histogram marks six skills ready to run once the extension and GitHub sign-in are in place, and one unverified; the skill's own description doesn't say what else it needs, so that one should be trusted less than the rest until it's checked directly.
WHAT'S INSIDE
7 showing · 7 totalReady to use
Nothing else to set up — install it and go.
7 of 7
SETUP
Showing all 7 skills
address-pr-comments
Reviewer feedback on a pull request is a dozen small edits scattered across files; this makes each one, touches nothing else, and closes the thread behind it.
create-pull-request
Opens a pull request on GitHub for the branch you are working on, with a title and summary written to tell the reviewer why the change is needed, not only what it does.
form-github-search-query
GitHub's search box has a syntax of its own; this turns what you asked for into that syntax, looking up the repository's real labels so it filters on ones that exist.
show-github-search-result
Takes a pile of GitHub search hits and lays them out as a table you can scan at a glance, each row linking back to the issue or pull request itself.
suggest-fix-issue
The hard part of a bug report is working out what is actually wrong; this reads the report and the discussion under it and comes back with a fix written against real files in your project.
summarize-github-issue-pr-notification
Boils a long GitHub issue, pull request, or notification down to its main points, keeping each remark attached to the person who made it.
write-changelog
Every release of the extension gets a written list of what changed, aimed at the people who use it rather than the people who built it — this assembles that list and files it at the top of the changelog.
No skill in this package matches that.
HOW TO GET IT
WHOLE PACKAGEInstall the whole package (7 skills)
npx skills add microsoft/vscode-pull-request-githubSINGLE SKILLOr install a single skill
npx skills add microsoft/vscode-pull-request-github --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.