Report VS Code endgame status, focusing on test-plan progress, tester activity, release-branch PRs, and release-build availability.
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Keep reports concise, linked, and read-only unless the user requests changes. Refresh GitHub and build data before each report, and give the observation time.
repo:microsoft/vscode is:issue is:open "Endgame" (for example, gh search issues 'repo:microsoft/vscode is:issue is:open "Endgame"' --json number,title,url). Confirm the release from the plan's title, milestone, and schedule rather than assuming the newest issue is the right one. If the user names a release, search for that version too; recovery plans can coexist with the main endgame.While testing is underway, make TPIs the main focus.
testplan-item in the milestone from both microsoft/vscode and microsoft/vscode-internalbacklog when authorized. Some TPIs exist only in the internal backlog; searching the public repository alone is incomplete. Disclose inaccessible sources or a user-selected cohort.endgame-tpi-progress skill from the endgame-tpi plugin to open the Endgame TPI Progress canvas (vscode-endgame-tpi) with a full progress-over-time chart. If unavailable, add a brief note directly below the numbers that the optional Endgame TPI plugin is needed, linking to the plugin installation guide. Do not install it automatically or generate a replacement app; the status report must not depend on the canvas.Once the testing day in the current plan has passed, list all open issues remaining on the milestone across both trackers when authorized, separated into:
candidate and/or linked to an open PR targeting the release branch. Link the PR and state which evidence puts the issue in this group.On Deck. Flag known blockers or unclear release intent rather than assuming they can be deferred.Include each issue's link and assignees. Account for TPIs and the endgame tracking issue too, but identify those as testing/process follow-up rather than suggesting they move to On Deck. These are recommendations only; do not change milestones without authorization.
Use one table for all unpublished release changes: open PRs targeting the release branch and merged PRs not yet included in a published release-branch build. Include columns for PR/change, author, and status (for example, awaiting review, CI failing/running, or merged awaiting publication). Do not split open and merged PRs into separate lists or tables. Once testing is complete, make this the main focus.
For bot-created cherry-picks/backports, follow the original PR link or cherry-picked commit to identify the original PR's author and credit that person instead of the bot when possible. Link the original PR as attribution evidence. If the original author cannot be verified, retain the known attribution and state the uncertainty rather than guessing.
Only list changes not yet included in a released build. Verify inclusion against the published build's source revision, including backport/cherry-pick equivalents when necessary; merge status or a successful build alone is not proof of publication. State when inclusion cannot be verified.
microsoft/vscode
278203b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.