update-screenshots

Download CI screenshot artifacts and commit updated baselines with LFS handling.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/colajacquin-e/ephcode --skill update-screenshots-colajacquin-e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-screenshots
Source: https://github.com/colajacquin-e/ephcode/tree/main/.github/skills/update-screenshots
Command: npx skills add https://github.com/colajacquin-e/ephcode --skill update-screenshots-colajacquin-e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Downloads and integrates the latest CI-generated screenshot baselines, ensuring local baselines reflect the true CI results and making it easy to commit updated assets when tests fail or diffs are reported.

Core Features & Use Cases

  • Retrieve the most recent screenshot-diff artifact from the Screenshot Tests workflow.
  • Replace local baselines with CI-produced screenshots and commit them, including guidance on Git LFS handling.
  • Provide a repeatable, auditable workflow for reviewing diffs, staging changes, and pushing updates to the repository.

Quick Start

Run the update-screenshots skill to fetch the latest CI baselines, review the diff, replace baselines, and push changes to the repository.

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 from CI artifacts when tests report diffs?

This Skill automates updating local screenshot baselines by pulling the latest CI-produced screenshot-diff artifacts, replacing local files, and committing them with proper Git LFS handling.

What do I need to download CI screenshots and refresh local baselines?

Downloading CI screenshots to refresh baselines requires gh CLI access to fetch the screenshot-diff artifact from the Screenshot Tests workflow, plus Git LFS configured for committing updated screenshot assets.

How does Git LFS handling work when committing updated screenshot baselines?

Git LFS handling ensures updated screenshot baselines are tracked as LFS objects when committing, requiring you to push LFS objects to the repository alongside the baseline replacement to maintain proper version control of large screenshot assets.

Can I automate pulling screenshot-diff artifacts from the Screenshot Tests workflow?

You can automate pulling screenshot-diff artifacts from the Screenshot Tests workflow using gh CLI access to retrieve the latest run artifact, then copy and commit updated baselines to keep local screenshots synchronized with CI results.

What's the best way to sync local screenshot baselines with latest CI runs?

The best way to sync local screenshot baselines with latest CI runs is to retrieve the screenshot-diff artifact, review differences, replace local baselines with CI-produced screenshots, and commit updated baselines while pushing LFS objects to the repository.

Why do my screenshot tests fail after CI produces new screenshot diffs?

Screenshot tests fail when local baselines differ from CI-produced screenshots, requiring you to retrieve the screenshot-diff artifact, review reported differences, replace local baselines with updated CI screenshots, and commit changes to resolve the mismatch.