android-snapshot-diff

Capture and diff Android UI snapshots to verify state changes.

7|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/himattm/skills --skill android-snapshot-diff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-snapshot-diff
Source: https://github.com/himattm/skills/tree/main/plugins/android/skills/android-snapshot-diff
Command: npx skills add https://github.com/himattm/skills --skill android-snapshot-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Snapshot Diff skill helps determine whether a state change actually occurred by capturing pre- and post-action snapshots (layout JSON, meminfo, getprop, and screenshot) and diffing them to provide a clear verdict on interactions, navigations, or fixes.

Core Features & Use Cases

  • Capture and compare UI layouts to confirm changes or regressions.
  • Diff memory and system prop data to detect leaks or behavioral differences.
  • Use across Android apps to verify fixes, rotations, and navigation flows with deterministic diffs.

Quick Start

Record a baseline A snapshot, perform the action, record a B snapshot, and compare them to determine if anything changed.

Frequently Asked Questions about android-snapshot-diff

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

FAQPage Schema
How do I verify an Android UI state change actually occurred after an interaction?

Verify Android UI state changes by capturing pre-action and post-action snapshots, then diffing layout JSON, dumpsys meminfo, getprop, and screenshots to provide a clear verdict on whether the interaction or navigation succeeded.

How do I detect Android memory leaks using snapshot diffs?

Detect Android memory leaks by capturing dumpsys meminfo snapshots before and after an action, then diffing the memory data to identify behavioral differences or leaks across repeated actions and rotation scenarios.

Can I compare Android layout JSON before and after a device rotation?

Compare Android layout JSON across rotation scenarios by recording a baseline snapshot before rotation and a second snapshot after, then diffing them to confirm state preservation or identify layout regressions deterministically.

What is the best way to confirm an Android navigation flow or fix worked?

Confirm Android navigation flows and fixes by following a repeatable A to B workflow: record a baseline A snapshot, perform the action, record a B snapshot, and compare the diffs to determine if anything changed.

Does this snapshot diff approach work for repeated actions and state preservation testing?

Snapshot diffs work for repeated actions and state preservation testing by capturing and comparing layout JSON, meminfo, getprop, and screenshots across iterations, providing deterministic diffs to verify UI flows and detect regressions.