update-screenshots

Downloads screenshot artifacts from CI runs and explains the external baseline service workflow.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/basedgod55hjl/vsbrax --skill update-screenshots-basedgod55hjl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-screenshots
Source: https://github.com/basedgod55hjl/vsbrax/tree/main/.github/skills/update-screenshots
Command: npx skills add https://github.com/basedgod55hjl/vsbrax --skill update-screenshots-basedgod55hjl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Component screenshot baselines are no longer stored in the repository, so developers need guidance on how the external screenshot service works and how to investigate visual differences reported by CI. ## Core Features & Use Cases - CI Artifact Download: Retrieves the raw captured screenshots from a GitHub Actions run using the gh CLI for local inspection. - Baseline Workflow Explanation: Documents that baselines are managed by an external screenshot service keyed by commit SHA, with automatic diffing and PR comments. - Use Case: After the Checking Component Screenshots action posts a visual diff comment on your PR, use this Skill to download the screenshots artifact and compare the captured images locally before merging. ## Quick Start Ask the agent to download the screenshots artifact from the failing CI run and explain the visual differences reported on the pull request.

Frequently Asked Questions about update-screenshots

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update component screenshot baselines from CI?

No manual baseline update is needed. The external screenshot service stores images keyed by commit SHA, and the screenshots on the main branch commit become the new baselines automatically after the PR is merged.

How to download screenshot artifacts from a GitHub Actions run?

Run gh run download <run-id> --name screenshots --dir .tmp/screenshots with the GitHub CLI. The artifact contains the full set of captured screenshots from that CI run for local comparison.

Where are screenshot baselines stored in this repository?

Baselines are not stored in the repository. They were removed from test/componentFixtures/.screenshots/baseline/ and are now managed by the external service hediet-screenshots.azurewebsites.net, with Git LFS no longer used.

Why does the Checking Component Screenshots action report differences?

The CI workflow uploads captured screenshots to the external service, which diffs them against stored baselines. When differences are detected, the action posts a PR comment with before and after comparisons for review.

Can I compare screenshot diffs locally before merging?

Yes. Download the screenshots artifact from the CI run using the gh CLI, then compare the captured images locally. The artifact contains the complete set of screenshots from that run.