skills.rest
voidful
voidfulCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

update-screenshots

Investigate component screenshot differences reported by CI and download captured artifacts.

1|Updated Apr 8, 2026
Search Tags:#screenshots#github actions#artifacts#visual testing#component testing#ci#baselines
One-click install
npx skills add https://github.com/voidful/Aixlarity --skill update-screenshots-voidful
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-screenshots
Source: https://github.com/voidful/Aixlarity/tree/main/aixlarity-ide/.github/skills/update-screenshots
Command: npx skills add https://github.com/voidful/Aixlarity --skill update-screenshots-voidful

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the component screenshot GitHub Action reports visual differences on a pull request, developers need a clear procedure to inspect the changes and retrieve the captured images without manually hunting through CI logs. ## Core Features & Use Cases - CI Baseline Workflow Guidance: Explains that screenshot baselines are managed by an external service (hediet-screenshots.azurewebsites.net) keyed by commit SHA, not stored in the repository. - Artifact Retrieval: Provides the exact gh run download <run-id> --name screenshots command to fetch raw captured screenshots from a CI run for local comparison. - Use Case: After the 'Checking Component Screenshots' action posts a PR comment with visual diffs, run this skill as a subagent to download the screenshots artifact and compare the images locally before merging. ## Quick Start Ask the agent to investigate the screenshot differences reported by the CI run and download the screenshots artifact for local comparison.

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?▼

Manual baseline updates are no longer needed. Baselines are managed by an external screenshot service keyed by commit SHA, and the screenshots on the main branch commit become the new baselines automatically after merge.

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 hosted on hediet-screenshots.azurewebsites.net, with Git LFS no longer used for screenshot storage.

What should I do when the screenshot test GitHub Action reports differences?▼

Check the PR comment posted by the CI workflow, which includes before/after visual comparisons. If deeper investigation is needed, download the screenshots artifact from the CI run and compare the images locally.

Does this workflow still use Git LFS for screenshots?▼

No. Git LFS is no longer used for screenshot storage. The external screenshot service stores images keyed by commit SHA and handles diffing automatically.

Related Skills

Explore More Software Engineering Skills→
posit-devposit-dev
4.2k

update-screenshots

Downloads screenshot artifacts from CI runs and reviews component screenshot diffs.

Official
Basic
mlopscommunitymlopscommunity
37

visual-regression

Capture UI screenshots with Playwright and compare visual differences between code versions.

Official
Advanced
LumenWipeLumenWipe
3

bench-skills

Benchmark local AI skills against held-out evaluation prompts with deterministic sampling.

Official
Advanced
iressiress
1

token-usage

Guide AI agents to apply IDS design tokens in React components and CSS.

Official
Advanced