update-screenshots

Updates committed blocks-ci screenshot hashes from CI job output after check failures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the "Screenshots & Tests" CI check fails because blocks-ci screenshot hashes no longer match the committed baseline file, someone must retrieve the new hashes from CI, verify the visual change is intentional, and update the committed file. This Skill guides that workflow so hashes are never regenerated locally (which would produce wrong values on non-Linux machines) and regressions are not blindly accepted. ## Core Features & Use Cases - Hash retrieval from CI: Pulls updated hashes from the PR comment, job summary, or job log using the GitHub CLI. - Visual verification: Fetches old and new screenshot images by hash from the external image service and diffs them with Python/Pillow to confirm the change is intentional. - Precise file updates: Edits only the changed lines in test/componentFixtures/blocks-ci-screenshots.md while preserving the auto-generated format, then commits and pushes. - Use Case: A PR fails the "Screenshots & Tests" check with a blocks-ci hash mismatch. Run this Skill to locate the failed job, extract the expected hashes, compare the before/after images, and commit the corrected baseline file. ## Quick Start Update the blocks-ci screenshot hashes for my PR after the Screenshots & Tests check failed.

Frequently Asked Questions about update-screenshots

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

FAQPage Schema
How do I update screenshot baselines after a CI failure?▼

Retrieve the updated hashes from the PR comment, job summary, or job log of the failed Screenshots & Tests check, then edit only the changed lines in test/componentFixtures/blocks-ci-screenshots.md and commit. Never regenerate hashes locally.

Why can't I regenerate screenshot hashes locally on macOS or Windows?▼

The hashes are computed from rendered PNG bytes produced on ubuntu-latest. Rendering on macOS or Windows yields different bytes and therefore different hashes, so locally generated values will fail CI.

How do I find the failed Screenshots & Tests job ID with GitHub CLI?▼

Run gh pr checks <PR> --json name,link,bucket and filter for the entry named Screenshots & Tests. Then use gh api repos/microsoft/vscode/actions/jobs/<JOB_ID>/logs to download the log and grep for the error lines.

How can I compare old and new screenshot images before accepting hashes?▼

Download both images by hash from hediet-screenshots.azurewebsites.net using curl, then use Python with Pillow's ImageChops.difference to compute the bounding box of changed pixels and confirm the delta matches the PR's intent.

When should I not update the screenshot hashes?▼

Do not update hashes when the visual change is unrelated to the PR, larger than expected, or when fixtures failed to render or Playwright tests failed. Those indicate genuine regressions that require fixing the code instead.