Update Screenshots
- 2k installs
- 188k repo stars
- Updated July 28, 2026
- microsoft/vscode
update-screenshots is an agent skill for 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-
About
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. The update-screenshots skill documents workflows and patterns from the repository SKILL.md. --- name: update-screenshots description: 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. --- # 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.
- Update Component Screenshots from CI
- 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.
- Check the PR comment posted by the CI workflow for visual diffs.
Update Screenshots by the numbers
- 2,004 all-time installs (skills.sh)
- +106 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #171 of 1,041 Cloud & Infrastructure skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
update-screenshots capabilities & compatibility
- Capabilities
- update component screenshots from ci · baseline images were removed from `test/componen · git lfs is no longer used for screenshot storage · the screenshot service stores images keyed by co · check the pr comment posted by the ci workflow f
- Use cases
- documentation
What update-screenshots says it does
--- name: update-screenshots description: 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.
--- # 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`).
npx skills add https://github.com/microsoft/vscode --skill update-screenshotsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2k |
|---|---|
| repo stars | ★ 188k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | microsoft/vscode ↗ |
What problem does update-screenshots solve for developers using the documented workflows?
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 re
Who is it for?
Developers working with update-screenshots patterns described in the skill documentation.
Skip if: Skip when docs are empty or the task is outside the skill documented scope.
When should I use this skill?
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 re
What you get
Grounded guidance and workflows from SKILL.md for update-screenshots.
- Updated screenshot baseline commits
Files
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
1. Check the PR comment posted by the CI workflow for visual diffs. 2. Download the screenshots artifact from the CI run for the raw captured images:
gh run download <run-id> --name screenshots --dir .tmp/screenshots3. Compare locally if needed. The artifact contains the full set of captured screenshots.
Related skills
Azure AiIntegrates Azure AI Content Safety, Document Intelligence, Speech, and Search services into Java-based agents and applications.479k1.3kAzure PrepareGenerate the exact Azure infrastructure files, Dockerfiles, and azure.yaml configuration needed before deploying any new or modernized application.479k1.3kAzure StorageConnect agents and applications to Azure Blob Storage, File Shares, Queues, Tables, and Data Lake without leaving the coding environment.478k1.3kAppinsights InstrumentationAutomatically instrument web applications running on Azure App Service with Application Insights for observability without manual configuration.478k1.3kAzure Resource LookupInstantly list, query, and discover any Azure resources across subscriptions without leaving the agent chat.478k1.3kAzure AigatewayConfigure Azure API Management as a secure, governed gateway for routing traffic to LLMs, MCP servers, and agent tools.478k1.3kHow it compares
Specific to the VS Code hediet-screenshots CI pipeline; not a general visual regression tool for other repositories.
FAQ
Who is Update Screenshots for?
Developers and software engineers working with update-screenshots patterns from the skill documentation.
When should I use 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. T
Is Update Screenshots safe to install?
Review the Security Audits panel on this page before installing in production.