agentleFS
Sign inStart free
OpenCortexIDEOpenCortexIDE/cortexide/.github/skills/update-screenshots/SKILL.md

update-screenshots

Skill175 starsChanged 8 months agoMITView on GitHub

Download 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.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When the Checking Component Screenshots GitHub Action detects changes, it posts a PR comment with before/after comparisons.

    line 10
  2. Distinctive:

    Check the PR comment posted by the CI workflow for visual diffs.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Update Component Screenshots from CI

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

  1. Check the PR comment posted by the CI workflow for visual diffs.
  2. Download the screenshots artifact from the CI run for the raw captured images:
gh run download <run-id> --name screenshots --dir .tmp/screenshots
  1. Compare locally if needed. The artifact contains the full set of captured screenshots.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free