Skip to content
TrustedSkillsbeta
Back to all skills

Snapshot Testing

Checked
aaronontheweb·vlatest·testing·MIT

Verify UI element states against baseline snapshots to quickly detect visual regressions during development.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add aaronontheweb/dotnet-skills --skill snapshot-testing -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

aaronontheweb

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned aaronontheweb/dotnet-skills at e426ed93a9.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
e426ed93a9
Manifest
skills/snapshot-testing/SKILL.md
Scanned
1 file, 371 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

Snapshot Testing

What it does

Snapshot testing captures the complete output of code execution, such as rendered UI components or API responses, and compares it against a stored reference image. It automatically detects visual regressions by flagging any differences between the current output and the saved baseline without requiring manual pixel-by-pixel inspection.

When to use it

  • UI Regression Detection: Verify that frontend components render exactly as intended after refactoring styles or logic.
  • API Contract Validation: Ensure backend response structures remain consistent when modifying data models or endpoints.
  • Visual Consistency Checks: Catch unintended layout shifts or color changes in complex dashboards during automated test suites.
  • Baseline Creation: Establish a "golden record" of expected behavior for critical user flows to prevent future drift.

Key capabilities

  • Generates and stores snapshot files representing the exact state of code output.
  • Automatically compares new runs against stored snapshots to identify discrepancies.
  • Highlights specific differences between the current output and the baseline image.
  • Supports integration into CI/CD pipelines for automated quality gates.

Example prompts

  • "Run a snapshot test on the login button component to ensure the recent CSS update didn't break the layout."
  • "Generate a new snapshot baseline for the user dashboard after adding the analytics widget."
  • "Compare the current API response from the /users endpoint against the stored snapshot and report any structural changes."

Tips & gotchas

Ensure your test environment is stable before creating baselines, as external factors like fonts or system fonts can cause false positives. Regularly review failed snapshots to distinguish between actual bugs and harmless output variations before updating the baseline.