OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add microsoft/vscode-pull-request-github --skill write-changelog
Write a CHANGELOG.md entry for a new extension release. Use when: writing changelog, updating changelog, adding release notes, preparing a release, documenting milestone changes. Requires a milestone name and extension version number.
npx skills add microsoft/vscode-pull-request-github --skill write-changelog
Generate a new entry in CHANGELOG.md for an extension release by gathering closed issues and merged PRs from a GitHub milestone.
The user must provide:
0.134.0)1.112.0)Search for all closed items in the milestone scoped to microsoft/vscode-pull-request-github:
milestone:"<name>" repo:microsoft/vscode-pull-request-github is:closedmilestone:"<name>" repo:microsoft/vscode-pull-request-github is:pr is:mergedSort every item into one of these buckets:
| Bucket | Criteria |
|---|---|
| Changes | Feature requests, enhancements, new settings, new commands, infrastructure improvements (e.g. dependency upgrades, build system changes) |
| Fixes | Items labeled bug, or PRs that fix a specific issue |
| Thank You | Merged PRs authored by external contributors (user type is not Bot, and user is not a GitHub staff / site_admin) |
| Skip | Version-bump PRs (title is just a version like "0.132.0"), test plan items, items from other repos |
Insert the new section at the top of CHANGELOG.md, directly after the # Changelog heading and before the previous release section.
Follow this format exactly:
- bullet.- bullet. If a fix came from a PR without a linked issue, describe it without a URL.* bullets (not - ). Format: [@login (Name)](profile-url): Description [PR #number](pr-url). Only include for external community contributors.### Changes, ### Fixes, **_Thank You_**) if there are no items for it.# Changelog, before the previous version).microsoft/vscode-pull-request-github.