Update Component Screenshots from CI
SkillAI & modelsDownload 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.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Update Component Screenshots from CI skill
What this skill tells your AI
The instructions your AI receives, as published by che-incubator/che-code in code/.github/skills/update-screenshots/SKILL.md and read by ahel’s review.
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
screenshotsartifact 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.
Signals
- GitHub stars
- 35
- Forks
- 50
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
update-screenshots- Source
- github.com/che-incubator/che-code