Methodologygeneric

update-screenshots

Download screenshot baselines from the latest CI run and commit them. Use when asked to update, accept, or refresh component screenshot baselines from CI, or after the screenshot-test GitHub Action reports differences. This skill should be run as a subagent.

microsoft/vscode

View source

Install

npx skills add https://github.com/microsoft/vscode --skill update-screenshots

Use with your agent

Install the update-screenshots skill, then use it as build context. Run: npx skills add https://github.com/microsoft/vscode --skill update-screenshots. Then read the installed skill.md and follow its guidance to build or refactor my project.

Update Component Screenshots from CI

Screenshot baselines are no longer stored in the repository. They are managed by an external screenshot service (hediet-screenshots.azurewebsites.net). The CI workflow uploads screenshots to this service and diffs them automatically.

When the Checking Component Screenshots GitHub Action detects changes, it posts a PR comment with before/after comparisons. No manual baseline updates are needed — the screenshots on the main branch commit become the new baselines automatically after merge.

What Changed

Baseline images were removed from test/componentFixtures/.screenshots/baseline/.
Git LFS is no longer used for screenshot storage.
The screenshot service stores images keyed by commit SHA and handles diffing.

If Screenshots Need Investigation

Check the PR comment posted by the CI workflow for visual diffs.
Download the screenshots artifact from the CI run for the raw captured images:

gh run download <run-id> --name screenshots --dir .tmp/screenshots

Compare locally if needed. The artifact contains the full set of captured screenshots.