Agent skill · microsoft
sweeper-implement
Implement a VS Code Sweeper agent-ready issue — fetch the sweeper's review record from its state repo, implement the change in the current vscode checkout from the review's brief (an implement-ready record) or from an approved sweeper-plan file, validate the diff against it, and — after the maintainer has reviewed the changes in their editor — open a draft PR. Use ONLY when the request explicitly asks for the sweeper — "sweeper-implement", "sweeper", "vscodesweeper", a sweeper record, an agent-ready issue, or a sweeper brief — or asks to implement a sweeper plan ("implement plan <n>", a `.sweeper/plans/issue-<n>.md` file). Do NOT use for a plain "fix this issue" request that doesn't mention the sweeper; fix those directly with your normal tools instead.
What it needs
About 9k tokens when loaded.
What this skill does
<!-- Generated by vscodesweeper (sweeper-implement skill v7) — do not edit by hand. Source: skills/sweeper-implement/SKILL.template.md in the vscodesweeper repo; getting started: https://egamma.github.io/vscodesweeper-state/fix-skill.html --> sweeper-implement — implement a sweeper-reviewed issue You are working on a single microsoft/vscode issue on behalf of the maintainer who invoked you. The VS Code Sweeper reviewed it, judged it agent-ready, and wrote a brief while tracing it in the source. You implement the issue and end in a draft PR the maintainer owns. What you implement from depends on the record's tier: implement record → the brief. The review did the diagnosis (confirmed defect, bounded change, a named validation); you turn the brief into the smallest correct change plus a test. There is no plan file (Sweeper mode: implement). plan record → the approved plan file, .sweeper/plans/issue-<issue-number>.md, written with the maintainer by the sweeper-plan skill; the maintainer asking you to implement it IS the approval (Sweeper mode: plan-first). Below, the spec means whichever of the two you are working from. You never plan a plan record yourself — that is the sweeper-plan skill's job. Keep the chat short: the maintainer reads the spec and the diff in their editor, not pasted into the conversation. Inside a question or choice prompt, write file paths as plain text — those prompts don't render markdown links. 0 · Preconditions (refuse if unmet) The working directory must be a microsoft/vscode checkout — git remote -v must list microsoft/vscode. If not, stop: "run this from your vscode checkout". The checkout must have no tracked modifications and no staged changes (git status --porcelain, ignoring untracked files). Dirty → stop and say so; do NOT stash, discard, or commit the maintainer's work-in-progress. Untracked files may stay — the ship step commits only files this skill created or edited. gh auth status must succeed (the gates and the PR need it). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills microsoft/sweeper-implement