| Skill | Added | Review |
|---|---|---|
smoke-tests .github/skills/smoke-tests/SKILL.md Use when running VS Code smoke tests or working on smoke-test CI steps. Covers pnpm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique for tracking down flaky smoke tests in CI. | 63 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: f357833 | |
sweeper-implement .github/skills/sweeper-implement/SKILL.md 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. | 76 Impact — No eval scenarios have been run Securityby Low Low-risk findings worth noting Version: f357833 | |
sweeper-plan .github/skills/sweeper-plan/SKILL.md Plan a VS Code Sweeper agent-ready issue with the maintainer — fetch the sweeper's review record from its state repo, put the review's open decisions to the maintainer, and write a plan file (.sweeper/plans/issue-<n>.md) for them to edit in their editor; it writes no code and ends there — the sweeper-implement skill implements the approved plan. Use ONLY when the request explicitly asks for the sweeper plan — "sweeper-plan", "plan … with the sweeper", a sweeper record or agent-ready issue to plan first. Do NOT use for a plain planning request that doesn't mention the sweeper. | 76 Impact — No eval scenarios have been run Securityby Low Low-risk findings worth noting Version: f357833 | |
symbolicate-crash-dump .github/skills/symbolicate-crash-dump/SKILL.md Symbolicate a native VS Code crash dump (.dmp) using electron-minidump. Use when given a crash dump file, asked to symbolicate a crash, resolve missing method names in a native crash backtrace, or attach Electron/Insiders/Stable symbol files. VS Code team members only; requires macOS or Linux. | 76 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: f357833 | |
unit-tests .github/skills/unit-tests/SKILL.md Use when running unit tests in the VS Code repo. Covers the runTests tool, scripts/test.sh (macOS/Linux) and scripts/test.bat (Windows), and their supported arguments for filtering, globbing, and debugging tests. | 64 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: f357833 | |
update-instructions .github/skills/update-instructions/SKILL.md update-instructions | 46 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: f357833 | |
update-screenshots .github/skills/update-screenshots/SKILL.md Update the committed blocks-ci screenshot hashes after the "Screenshots & Tests" check fails, or investigate a screenshot diff reported on a PR. Use when asked to update, accept, or refresh component screenshot baselines from CI. This skill should be run as a subagent. | 75 Impact — No eval scenarios have been run Securityby Low Low-risk findings worth noting Version: f357833 | |
ux-css-layout .github/skills/ux-css-layout/SKILL.md VS Code CSS conventions, file organization, class naming, standard sizes, SplitView/Grid layout, scrollable content, responsive layout, and text overflow/ellipsis patterns. Use when writing CSS, building layouts, or fixing text truncation issues. | 68 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: f357833 |