Individual skill

snapshot-testing-auditor

Audits brittle UI and JSON snapshot tests to eliminate false alarm failures and replace them with resilient semantic assertions.

skills/testing/snapshot-testing-auditor/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Audit test suites for brittle, oversized snapshot tests (Jest/Vitest `toMatchSnapshot()`) that create false alarms during trivial styling updates, blind `-u` approval habits, and slow CI runs, replacing them with precise semantic assertions.

## When to Use

- Developers routinely run `jest -u` without reading git diffs because snapshots break on every commit.
- Huge 500-line JSON/HTML snapshots stored in repository bloating git history.
- Distinguishing when inline snapshot testing is valuable vs when it provides illusory test coverage.

## What to Analyze

1. **Snapshot Granularity**: Giant DOM tree snapshots vs targeted component state / schema snapshots.
2. **Volatile Data**: Dynamic dates, random UUIDs, or counter variables causing non-deterministic snapshot diffs.