managing-snapshot-tests

This skill enables Claude to manage and update snapshot tests using intelligent diff analysis and selective updates. It is triggered when the user asks to analyze snapshot failures, update snapshots, or manage snapshot tests in general. It helps distinguish intentional changes from regressions, selectively update snapshots, and validate snapshot integrity. Use this when the user mentions "snapshot tests", "update snapshots", "snapshot failures", or requests to run "/snapshot-manager" or "/sm". It supports Jest, Vitest, Playwright, and Storybook frameworks.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill managing-snapshot-tests

What are skills?

1.00x

Review — 53%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Evaluation — 96%

↑ 1.00x

Agent success when using this skill

Validation — 11 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Evaluation results

100%

Snapshot Triage After a UI Redesign

Selective snapshot update vs blind update

Criteria

Without context

With context

Selective update only

100%

Suspicious snapshot preserved

100%

Intentional vs unrelated distinction

100%

Does not update all snapshots

100%

Analysis document produced

100%

Update rationale for each snapshot

100%

Jest framework used correctly

100%

Button and Form snapshots updated

100%

Layout snapshot NOT updated

100%

Diff analysis present

100%

Without context: $0.2755 · 2m 41s · 16 turns · 17 in / 3,924 out tokens

With context: $0.3660 · 2m 50s · 20 turns · 52 in / 4,387 out tokens

100%

Snapshot Failure Investigation for a Shared Component Library

Diff analysis with regression identification

Criteria

Without context

With context

Before/after comparison

100%

Unexpected change flagged

100%

Expected changes identified

100%

Unexpected change for review

100%

Vitest framework awareness

75%

100%

Update intention stated

100%

No mass-update

100%

Summary table or list

100%

Padding snapshots updated

100%

Empty state snapshot NOT updated

100%

Without context: $0.3884 · 3m 20s · 19 turns · 20 in / 5,416 out tokens

With context: $0.3476 · 2m 58s · 19 turns · 18 in / 4,452 out tokens

98%

Snapshot Maintenance After Design Token Migration

Batch update and snapshot integrity validation

Criteria

Without context

With context

Batch grouping applied

66%

100%

Batch rationale documented

75%

100%

Problematic snapshot identified

100%

Quality observation reported

100%

Jest framework awareness

62%

75%

Selective within batch

100%

Color token snapshots updated

100%

Process log produced

100%

Diff analysis per snapshot

100%

Internal state snapshot not updated

100%

Without context: $0.2198 · 2m 40s · 13 turns · 14 in / 3,753 out tokens

With context: $0.4874 · 3m 54s · 24 turns · 24 in / 6,540 out tokens

97%

-1%

Accessibility Audit Snapshot Review

Playwright framework snapshot handling

Criteria

Without context

With context

Playwright format awareness

80%

Main nav snapshot updated

100%

Footer nav snapshot updated

100%

Mobile menu snapshot NOT updated

100%

Regression flagged

100%

Intentional vs regression distinction

100%

Does not update all snapshots

100%

Side-by-side or before/after diff

100%

87%

Decision rationale per snapshot

100%

Analysis document produced

100%

Without context: $0.3199 · 3m 12s · 16 turns · 17 in / 4,373 out tokens

With context: $0.4097 · 3m 37s · 24 turns · 23 in / 4,682 out tokens

96%

Design Token Migration: Storybook Snapshot Cleanup

Storybook framework snapshot handling

Criteria

Without context

With context

Storybook format awareness

100%

90%

Batch grouping applied

66%

75%

Batch rationale documented

100%

Token snapshots updated

100%

Modal snapshot NOT updated

100%

Regression identified

100%

No mass update

100%

Process log produced

100%

Decision per story

100%

Diff description per snapshot

100%

Without context: $0.2563 · 2m 14s · 12 turns · 13 in / 3,504 out tokens

With context: $0.3900 · 3m 18s · 21 turns · 20 in / 4,981 out tokens

95%

Snapshot Update Proposal for PR Review

Side-by-side diff presentation and update intent documentation

Criteria

Without context

With context

Side-by-side format used

75%

83%

Intent stated per snapshot

100%

Unexpected change flagged for review

100%

Expected snapshots proposed for update

100%

Does not update all snapshots

100%

Summary table or list

100%

Clear communication of intent

100%

Vitest framework awareness

62%

Regression description

100%

Proposal document produced

100%

Without context: $0.1572 · 1m 24s · 8 turns · 9 in / 2,494 out tokens

With context: $0.3096 · 2m 17s · 16 turns · 15 in / 3,990 out tokens

90%

-1%

Snapshot Failures After Pulling Latest Main

All-regression snapshot investigation

Criteria

Without context

With context

No snapshot files updated

100%

All changes flagged for review

58%

33%

Footer regression identified

100%

UserCard regression identified

100%

Before/after comparison present

100%

Intentional vs unintentional framing

100%

Recommendation per snapshot

100%

Summary section present

100%

Jest framework conventions referenced

42%

71%

No mass-update recommended

100%

Without context: $0.2140 · 1m 23s · 9 turns · 10 in / 4,156 out tokens

With context: $0.2917 · 2m 19s · 12 turns · 44 in / 4,705 out tokens

92%

-8%

Snapshot Test Failures in Inherited Codebase

Framework identification and targeted updates

Criteria

Without context

With context

Vitest framework identified

100%

Vitest CLI referenced

100%

Card snapshots updated

100%

Input snapshot updated

100%

Divider snapshot updated

100%

Modal snapshot NOT updated

100%

Modal suspicious change flagged

100%

Before/after diff shown

100%

Vitest snapshot header preserved

100%

Rationale per snapshot

100%

Without context: $0.4230 · 3m 30s · 19 turns · 20 in / 6,590 out tokens

With context: $0.4806 · 3m 39s · 27 turns · 23 in / 7,134 out tokens

100%

Diagnosing Flaky Snapshot Tests

Brittle snapshot detection and audit

Criteria

Without context

With context

No snapshot files modified

100%

Tooltip volatile ID flagged

100%

ActivityFeed timestamp flagged

83%

100%

StyledButton CSS hash flagged

100%

Alert render-count and ID flagged

100%

Badge and DataTable empty state identified as stable

100%

DataTable row IDs assessed correctly

100%

Remediation recommendations present

100%

Audit report produced

100%

Summary table or list present

100%

Without context: $0.2772 · 3m 20s · 10 turns · 11 in / 6,010 out tokens

With context: $0.5575 · 4m 7s · 22 turns · 22 in / 9,169 out tokens

Evaluated: 3 days ago
Agent: Claude Code

Table of Contents

Snapshot Triage After a UI Redesign Snapshot Failure Investigation for a Shared Component Library Snapshot Maintenance After Design Token Migration Accessibility Audit Snapshot Review Design Token Migration: Storybook Snapshot Cleanup Snapshot Update Proposal for PR Review Snapshot Failures After Pulling Latest Main Snapshot Test Failures in Inherited Codebase Diagnosing Flaky Snapshot Tests

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.