argent-screenshot-diff

Compares baseline and current app screenshots to detect pixel-level visual regressions.

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/Seyamalam/pstu_final --skill argent-screenshot-diff-seyamalam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: argent-screenshot-diff
Source: https://github.com/Seyamalam/pstu_final/tree/main/.agents/skills/argent-screenshot-diff
Command: npx skills add https://github.com/Seyamalam/pstu_final --skill argent-screenshot-diff-seyamalam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? UI changes can silently break layout, spacing, color, typography, or rendering on mobile screens, and manual inspection often misses subtle pixel-level regressions. This Skill provides a deterministic screenshot comparison workflow that produces visual diff evidence for before/after UI verification. ## Core Features & Use Cases - Visual Regression Comparison: Compare a saved baseline PNG against a live-captured current screenshot, or compare two saved screenshot files directly. - Full-Resolution Capture Guidance: Capture baseline and current images at scale 1.0 with image output suppressed from context, keeping comparisons accurate and context usage low. - Diff Artifact Output: Produce diff summaries and artifact files in a specified output directory for review alongside structural and runtime evidence. - Use Case: After changing a screen's layout, capture the pre-change baseline, apply the change, then run the diff to confirm only the intended pixels changed and no unintended regression occurred elsewhere on the screen. ## Quick Start Capture a full-resolution baseline screenshot of the screen, make your UI change, then ask the assistant to run a screenshot diff comparing the saved baseline against the current screen on the device.

Frequently Asked Questions about argent-screenshot-diff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a visual regression test on a mobile app screen?

Capture a full-resolution baseline screenshot of the known-good state, apply your change or interaction, then call screenshot-diff with the baseline path, captureCurrent set to true, the device UDID, and an output directory. Inspect the diff summary and artifacts alongside normal visual inspection.

How to compare two saved screenshot files for UI differences?

Provide both file paths to screenshot-diff using baselinePath and currentPath, along with the device UDID and an outputDir. The tool compares the two PNGs and writes diff artifacts and a summary to the output directory.

When should I not use screenshot diffing for UI verification?

Avoid it when the result is better verified structurally, such as state changes, navigation existence, accessibility tree contents, or console and network behavior. It is also a poor fit when screens contain dynamic content, unpausable animations, timestamps, ads, or random data that make comparisons noisy.

Can screenshot diff be used to find tap coordinates on screen?

No, screenshot diffing should not be used for tap-coordinate discovery. Use describe, debugger-component-tree, or native-describe-screen to locate targets first, then use screenshot comparison only for pixel-level visual verification.

Why are my screenshot diff results noisy or meaningless?

Noise usually comes from unstable screens with animations, timestamps, or random data, or from mismatched capture resolutions. Capture both images at scale 1.0 in a stable state, and ensure the baseline is taken before the relevant interaction or code change.