Skip to content
Skills Library
Programming · Testing

diffglow

/diffglow

Integrate Diffglow with existing E2E screenshot tooling, or verify a UI change through intent, captures, visual evidence, agent feedback, and reruns. Use for Playwright, Maestro, or other screenshot-producing suites; preserve the existing test runner.

Repository
diffglow ↗
Licence
Apache-2.0
Last repository change
23.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
5
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Integrate Diffglow with existing E2E screenshot tooling, or verify a UI change through intent, captures, visual evidence, agent feedback, and reruns. Use for Playwright, Maestro, or other screenshot-producing suites; preserve the existing test runner.

Original author description

Integrate Diffglow with existing E2E screenshot tooling, or verify a UI change through intent, captures, visual evidence, agent feedback, and reruns. Use for Playwright, Maestro, or other screenshot-producing suites; preserve the existing test runner.

How it works

  1. Find the integration point
  2. Integrate with the current CLI
  3. Verify the change
  4. Handoff and references
Original SKILL.md headings · 169 lines, 1,321 words
SKILL.md preview
---
name: diffglow
description: Integrate Diffglow with existing E2E screenshot tooling, or verify a UI change through intent, captures, visual evidence, agent feedback, and reruns. Use for Playwright, Maestro, or other screenshot-producing suites; preserve the existing test runner.
---

# Diffglow

Use the customer's existing E2E tools to capture screenshots and Diffglow to
compare them. Use your own image-reading capabilities to assess visual intent.
The workflow is **intent → existing E2E captures → evidence → agent feedback →
rerun**. Routine changes do not require a separate snapshot approval ceremony.

## Find the integration point

Inspect the project's instructions, package manager, existing test commands,
screenshot checkpoints, CI jobs, and available reference captures. Preserve the
chosen runner and its assertions. Add named screenshot checkpoints only where
the requested coverage is missing; do not replace a working E2E suite.

- For Playwright, read [references/playwright.md](references/playwright.md).
- For Maestro, read [references/maestro.md](references/maestro.md).
- For verification plans and evidence reports, read
  [references/verification.md](references/verification.md).
- For another runner, use its existing screenshot output and the same file or
  folder comparison interface. Do not require browser-only metadata for mobile.

Prefer the project's installed, pinned Diffglow command. If installing it is part
of the request, use the project's package manager and record the resolved version
in its lockfile. Diffglow requires Node.js 22+. Check that version's `--help`
before configuring commands. Keep the skill usable independently of a particular
coding-agent vendor or hosted model provider.

## Integrate with the current CLI

Diffglow accepts PNG/JPEG files, two folders, a root with `baseline/` and `current/`,
or explicit JSON pairs. Names and variants must identify the same checkpoint
across runs. Separate browser/device, viewport, locale, and theme where relevant;
keep timestamps and run IDs out of checkpoint identity.

For an installed command, an evidence-producing invocation is:

```sh
diffglow captures/base captures/candidate --html --json --output-dir artifacts/diffglow/run-001
```

Adapt paths and the invocation to the existing project. Preserve stdout JSON and
the complete report directory, including assets, even if a comparison or E2E job
fails. Use a distinct report directory per run and keep verification plans and
agent reports outside the generated directory: rerunning replaces that directory.
Keep generated captures out of source control unless project policy says otherwise.

For reports that will be shared, add `--relative` to omit local absolute paths.
Use `--max-height 1200 --image-format webp` to reduce bundled report assets;
WebP is lossless, and the height limit preserves aspect ratio without enlarging
images. These settings leave comparison pixels and statistics at full resolution.
Keep the original captures for fine visual assessment: a reduced report image
cannot establish that small text or layout details are correct. Review screenshot
contents and user-supplied comparison IDs before sharing; path presentation does
not remove private content from either.

For known dynamic areas such as a mobile status-bar clock, use a narrow rectangle
in normalized screenshot pixels:

```sh
diffglow captures/base captures/candidate --ignore-region '0,0,160,60' --html --json --output-dir artifacts/diffglow/run-002
```

Repeat `--ignore-region 'x,y,width,height'` for multiple areas, or configure
`"ignoreRegions": [{"x": 0, "y": 0, "width": 160, "height": 60}]` in JSON.
Coordinates start at the top-left after orientation normalization, using actual
image pixels rather than CSS/device-independent coordinates. Positions must be
nonnegative integers and dimensions positive integers, with safe integer sums.
Rectangles clip to image coverage and overlapping pixels count once. CLI regions
replace the configured global `ignoreRegions` array; all configured values must
still be valid.

For different screenshot geometries, configure `ignoreRegionsById` glob rules or
add `ignoreRegions` to individual manifest pairs. Effective masks combine the
selected global array, every matching ID rule, and the pair's manifest regions.
CLI global replacements do not remove ID rules or pair regions. ID rules match
the comparison identity: the relative filename, a configured pairing key, or the
explicit manifest ID. For example:

```json
{
  "ignoreRegionsById": {
    "catalog/*.png": [{ "x": 720, "y": 340, "width": 180, "height": 48 }],
    "checkout-ready/ios/**": [{ "x": 0, "y": 0, "width": 160, "height": 60 }]
  }
}
```

Load these rules with `--config path/to/diffglow.config.json`, or use the single
input folder's automatically loaded `diffglow.config.json`. Diffglow does not
detect clocks automatically or resolve element selectors from screenshot pixels.
The existing capture tool can measure an element's rectangle and supply its
coordinates as a manifest mask.

Record the regions with the evidence and inspect that they do not hide relevant
UI. Masks change comparison only, **not screenshot redaction**: original values
remain visible in report previews. Ignored pixels retain current-image appearance,
are not highlighted, and are excluded from changed/unchanged/compared counts and
bounds. Each result records its effective `comparison.ignoreRegions` and
`stats.ignoredPixels`; batch `comparison.ignoreRegions` contains the global array,
and `summary.ignoredPixels` totals ignored pixels. HTML displays the exclusions.
If no pixels remain, the percentage is `0` and `--fail-on-diff` exits `0`, but the
visual check is inconclusive. Added/removed file statuses still describe coverage and require
interpretation even when all of their pixels are ignored.

Exit `0` means the comparison completed, even if images differ. With
`--fail-on-diff`, exit `1` means non-ignored raw differences were found; it does not
establish that they are regressions. Exit `2` means processing failed. Record E2E results
separately so a completed comparison cannot hide a failed test run. Preserve any
existing strict visual gate; do not turn it green by swallowing failures.

The CLI currently produces pixel evidence, not an AI verdict. It has no supported
JavaScript import API, semantic `verify` command, approval command, or automatic
baseline history. Plans and agent reports below are skill-authored artifacts,
separate from CLI `results.json`. If asked for an enforced semantic CI check,
identify that additional implementation explicitly; prose from this skill is
not an executable gate or independent verification service.

## Verify the change

1. Derive expected effects and protected behavior from the original request,
   acceptance criteria, and existing tests. Save that plan before inspecting the
   candidate images. If implementation already exists, record that fact and use
   the original requirements rather than treating the patch as proof of intent.
   Do not broaden expectations, masks, or tolerances to explain away a failure.
2. Obtain reference and candidate captures from the existing E2E workflow under
   matching render conditions. Record source revisions, runner outcomes, capture
   hashes, expected checkpoint coverage, and comparison settings. Confirm the
   images show the declared checkpoint/state; filenames alone do not establish
   that the correct screen was captured. Never label
   synthetic fixtures or two copies of the same capture as real before/after
   application evidence. If the reference or runner is unavailable, make useful
   integration changes and report the missing execution as inconclusive.
3. Check completeness before interpreting folder additions/removals. A missing
   screenshot may mean a skipped/failed test or absent shard. Require explicit
   scope/completion information for deletions; do not remove references based on
   absence alone. Aggregate compatible shards and identify retry attempts without
   selecting whichever image happens to pass.
4. Read the original before/after images and highlighted diff. Examine changed
   areas at sufficient resolution and keep whole-screen context. Pixel counts
   establish change, not correctness. Verify text, geometry, state, and visibility
   with supplied runner assertions or element metadata where available. Report
   screenshot-only judgments as model-assessed; an accessibility assertion alone
   does not prove the absence of visual clipping or overlap.
5. Return per-check **passed**, **failed**, or **inconclusive**, with evidence and
   verification method. A measured failure cannot be waived by model opinion.
   Missing coverage, unreadable evidence, or an ambiguous requirement stays
   inconclusive. Never invent model confidence percentages or claim the whole
   application is correct because captured checkpoints passed.
6. Fix demonstrated defects within the authorized task, then rerun the relevant
   existing E2E tests and comparison. Preserve earlier evidence, bound retries,
   and stop when checks pass or further progress needs missing infrastructure,
   product clarification, or authorization beyond the task. Report unresolved
   issues instead of weakening the checks.

## Handoff and references

Summarize intended effects verified, unexpected changes, failed/incomplete tests,
coverage limits, and links to the evidence. Keep raw diff status distinct from
the agent's semantic verdict. An integration-only request can be complete while
real application verification remains unexecuted; say which was achieved.

Use the project's established reference/history process if one exists. Do not
overwrite references merely to make a comparison pass. If automatic advancement
is requested, bind it to the exact verified capture hashes and the project's
normal trusted merge/check process, preserving previous revisions. Changes to
the images, reference, expectations, or settings invalidate affected conclusions.
Do not introduce manual per-snapshot approvals as the default workflow.
Files in this package (5)
  • SKILL.md 10 KB
  • agents/openai.yaml 1 KB
  • references/maestro.md 6 KB
  • references/playwright.md 6 KB
  • references/verification.md 6 KB

Versions

The database has no other skills named diffglow.

Database snapshot: 13.11.2026 · package version 0a2cf00f4735 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100visual-verify
    This skill should be used when verifying UI changes visually. Mobile prefers Maestro MCP with Maestro CLI fallback. Web uses Playwright MCP. macOS prefers Peekaboo MCP with the peekaboo CLI fallback. Provides patterns for availability probes, path selection, ephemeral/inline…
  • 100teach-maestro
    Use when starting a new project with Maestro or when no .maestro.md context file exists yet. Run once per project.
  • 100mobile-sim-verification
    Verify apps/mobile behavior end-to-end on the iOS simulator against a local API and relay, with Maestro for input and a stand-in host instead of a second machine. Use when asked to verify, reproduce, screenshot, or edge-test a mobile change in the real app rather than in tests.
  • 100playwright-testing
    UI/E2E test automation with Playwright MCP. Use when the user asks to "test the UI", "automate browser tests", "check the page", "take a screenshot", "run Playwright", "write E2E tests", or anything about browser-based testing.
  • 100playwright-e2e
    End-to-end test and click-verify a web app with Playwright — write specs, drive authenticated pages, screenshot, and run in CI. Use when a web change has to be proven in a real browser rather than by unit tests.
  • 100test-visual-regression
    Set up Playwright screenshot baselines and CI diffing so UI changes fail pixel by pixel instead of by eye. Use when "add visual regression tests" or "catch UI regressions". Functional clicks → test-playwright.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.