What problem does it solve? When the "Screenshots & Tests" CI check fails because rendered component screenshot hashes no longer match the committed baseline file, developers need a safe, verified way to accept the new hashes without regenerating them locally or blindly approving visual regressions. ## Core Features & Use Cases - CI Hash Retrieval: Pull the expected screenshot hashes from the PR comment, job summary, or job log using the GitHub CLI, since locally rendered hashes differ across platforms. - Visual Verification: Download old and new images by hash from the screenshot service and compute a pixel-level diff bounding box with Python and Pillow to confirm the change is intentional. - Precise Baseline Update: Edit only the changed lines in test/componentFixtures/blocks-ci-screenshots.md while preserving its auto-generated format, then commit so the check passes. - Use Case: A PR fails the "Screenshots & Tests" check with a blocks-ci hash mismatch. Run this Skill to fetch the CI-produced hashes, visually confirm the one-pixel shift matches the intended UI change, update the baseline file, and push. ## Quick Start Update the blocks-ci screenshot baselines for my PR after the Screenshots & Tests check failed, verifying the image diffs before committing the new hashes.
