agentleFS
godhiraj-codegodhiraj-code/greenbuild-plugin/skills/visual-testing/SKILL.md

visual-testing

Skill1 starsChanged 28 days agoMITView on GitHub

Add visual regression testing with Playwright screenshots, Applitools, Percy, or open-source diffing, with stable baselines and low false positives.

5 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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Update baselines on purpose with npx playwright test --update-snapshots, and review the diff in the PR.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

Visual testing

  1. Decide what a screenshot should prove: layout and branding of key pages and components, not dynamic data.
  2. Playwright built-in:
await expect(page).toHaveScreenshot('checkout.png', {
  mask: [page.getByTestId('timestamp')], maxDiffPixelRatio: 0.01, animations: 'disabled' });

Update baselines on purpose with npx playwright test --update-snapshots, and review the diff in the PR. 3. Make it stable: fixed viewport, fonts and locale; seeded data; mocked time; masked or hidden dynamic regions; generate baselines on the same OS/browser as CI (e.g. in the Playwright Docker image). 4. Hosted tools: Applitools Eyes (Visual AI match levels), Percy (BrowserStack), Sauce Visual. Use them for cross-browser coverage and a review workflow. 5. Python/Selenium: compare against reviewed baselines with a diff library (e.g. Visual Guard, see tools-and-libraries). 6. Review flow: a diff fails the build → a human accepts the new baseline or files a bug. Never auto-accept.

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.