intent-solutions-io/managing-snapshot-tests
010-archive/backups-20251108/skill-structure-cleanup-20251108-073936/plugins/testing/snapshot-test-manager/skills/snapshot-test-manager/SKILL.md
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 --global
skillsauthnpx skillsauth add intent-solutions-io/plugins-nixtla managing-snapshot-testsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 5, 2026, 7:07 AM14.9s4 files scanned
SKILL.md
- name:
- managing-snapshot-tests
- description:
- |
- allowed-tools:
- Read, Bash, Grep, Glob
- version:
- 1.0.0
Overview
This skill empowers Claude to efficiently manage snapshot tests by analyzing differences, selectively updating snapshots based on intentional changes, and identifying potential regressions. It provides a streamlined approach to maintain snapshot test suites across various JavaScript testing frameworks.
How It Works
- Analyzing Failures: Reviews failed snapshot diffs, highlighting intentional and unintentional changes with side-by-side comparisons.
- Selective Updating: Updates specific snapshots that reflect intentional UI or code changes, while preserving snapshots that have caught regressions.
- Batch Processing: Allows for batch updating of related snapshots to streamline the update process.
When to Use This Skill
This skill activates when you need to:
- Analyze snapshot test failures after code changes.
- Update snapshot tests to reflect intentional UI changes.
- Identify and preserve snapshots that are catching regressions.
Examples
Example 1: Updating Snapshots After UI Changes
User request: "I've made some UI changes and now my snapshot tests are failing. Can you update the snapshots?"
The skill will:
- Analyze the snapshot failures, identifying the diffs caused by the UI changes.
- Update the relevant snapshot files to reflect the new UI.
Example 2: Investigating Unexpected Snapshot Changes
User request: "My snapshot tests are failing, but I don't expect any UI changes. Can you help me figure out what's going on?"
The skill will:
- Analyze the snapshot failures, highlighting the unexpected diffs.
- Present the diffs to the user for review, indicating potential regressions.
Best Practices
- Clear Communication: Clearly state the intention behind updating or analyzing snapshots.
- Framework Awareness: Specify the testing framework (Jest, Vitest, etc.) if known for more accurate analysis.
- Selective Updates: Avoid blindly updating all snapshots. Focus on intentional changes and investigate unexpected diffs.
Integration
This skill works independently but can be used in conjunction with other code analysis and testing tools to provide a comprehensive testing workflow.
Related Skills
intent-solutions-io/managing-test-environments
testing
VerifiedTrustedCommunity
This skill enables Claude to manage isolated test environments using Docker Compose, Testcontainers, and environment variables. It is used to create consistent, reproducible testing environments for software projects. Claude should use this skill when the user needs to set up a test environment with specific configurations, manage Docker Compose files for test infrastructure, set up programmatic container management with Testcontainers, manage environment variables for tests, or ensure cleanup after tests. Trigger terms include "test environment", "docker compose", "testcontainers", "environment variables", "isolated environment", "env-setup", and "test setup".
6SKILL.mdUpdated Jun 5, 2026
intent-solutions-io/generating-test-doubles
tools
VerifiedTrustedCommunity
This skill uses the test-doubles-generator plugin to automatically create mocks, stubs, spies, and fakes for unit testing. It analyzes dependencies in the code and generates appropriate test doubles based on the chosen testing framework, such as Jest, Sinon, or others. Use this skill when you need to generate test doubles, mocks, stubs, spies, or fakes to isolate units of code during testing. Trigger this skill by requesting test double generation or using the `/gen-doubles` or `/gd` command.
6SKILL.mdUpdated Jun 5, 2026
intent-solutions-io/generating-test-data
tools
VerifiedTrustedCommunity
This skill enables Claude to generate realistic test data for software development. It uses the test-data-generator plugin to create users, products, orders, and custom schemas for comprehensive testing. Use this skill when you need to populate databases, simulate user behavior, or create fixtures for automated tests. Trigger phrases include "generate test data", "create fake users", "populate database", "generate product data", "create test orders", or "generate data based on schema". This skill is especially useful for populating testing environments or creating sample data for demonstrations.
6SKILL.mdUpdated Jun 5, 2026
intent-solutions-io/analyzing-test-coverage
development
VerifiedTrustedCommunity
This skill analyzes code coverage metrics to identify untested code and generate comprehensive coverage reports. It is triggered when the user requests analysis of code coverage, identification of coverage gaps, or generation of coverage reports. The skill is best used to improve code quality by ensuring adequate test coverage and identifying areas for improvement. Use trigger terms like "analyze coverage", "code coverage report", "untested code", or the shortcut "cov".
6SKILL.mdUpdated Jun 5, 2026