managing-snapshot-tests
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill managing-snapshot-testsThis 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.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill content describes what snapshot management should do rather than instructing Claude how to do it. It lacks any executable code, specific commands, or concrete workflows. The content reads like marketing copy rather than actionable technical guidance.
Suggestions
Add concrete, executable commands for each supported framework (e.g., `npx jest -u path/to/test.js`, `npx vitest -u`)
Include a specific workflow with validation steps: how to identify which snapshots changed, how to review diffs, criteria for deciding to update vs investigate
Provide actual code examples showing how to analyze snapshot diff output and make update decisions
Remove explanatory filler text ('This skill empowers', 'streamlined approach') and replace with direct instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what snapshot tests are, how diffs work). Phrases like 'This skill empowers Claude' and 'streamlined approach' are filler. The entire document could be reduced to a fraction of its size. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The examples describe what 'the skill will' do abstractly rather than showing actual commands, code snippets, or specific steps Claude should take. No framework-specific commands (e.g., `jest -u`, `vitest -u`) are included. | 1 / 3 |
Workflow Clarity | Steps are vague and lack specificity. 'Analyze the snapshot failures' and 'Update the relevant snapshot files' provide no actual workflow. No validation checkpoints, no commands to run, no criteria for distinguishing intentional changes from regressions. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with clear headers, but it's a monolithic document with no references to external files for framework-specific details or advanced usage. The structure exists but content that could be split (framework-specific commands) is missing entirely. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes natural trigger terms users would actually say, explicitly states when to use it, and carves out a distinct niche around snapshot testing. The inclusion of supported frameworks and command shortcuts further strengthens its utility for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'manage and update snapshot tests', 'intelligent diff analysis', 'selective updates', 'distinguish intentional changes from regressions', 'validate snapshot integrity'. Also specifies supported frameworks (Jest, Vitest, Playwright, Storybook). | 3 / 3 |
Completeness | Clearly answers both what (manage/update snapshots, diff analysis, selective updates, validate integrity) AND when with explicit 'Use this when...' clause listing specific trigger phrases and commands. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'snapshot tests', 'update snapshots', 'snapshot failures', '/snapshot-manager', '/sm'. These are terms developers naturally use when working with snapshot testing. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on snapshot testing with distinct triggers like '/snapshot-manager', '/sm', and snapshot-specific terminology. Unlikely to conflict with general testing or code review skills. | 3 / 3 |
Total | 12 / 12 Passed |
Reviewed
Table of Contents
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.