insta-snapshots

Manage insta snapshot tests non-interactively in the Oxc codebase.

22.3k|1.2k|Updated Feb 9, 2023
One-click install
npx skills add https://github.com/oxc-project/oxc --skill insta-snapshots
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: insta-snapshots
Source: https://github.com/oxc-project/oxc/tree/main/.agents/skills/insta-snapshots
Command: npx skills add https://github.com/oxc-project/oxc --skill insta-snapshots

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams to work with insta snapshot tests in Oxc without requiring terminal interaction, reducing bottlenecks in test maintenance.

Core Features & Use Cases

  • Non-interactive review of insta snapshots across crates, including linter and semantic tests.
  • Read and compare .snap and .snap.new files, identify changes, and prepare them for review.
  • Accept or reject pending snapshots and verify changes with git diffs to ensure traceability.

Quick Start

Generate new snapshots by running tests, then review and non-interactively accept or reject changes.

Frequently Asked Questions about insta-snapshots

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate insta snapshot updates without terminal interaction?

To update insta snapshots non-interactively, this skill reads and compares `.snap` and `.snap.new` files, enforces pending-snapshots usage, and applies changes across linter and semantic crates without manual terminal steps.

How do I review and accept pending insta snapshots in a Rust codebase?

Reviewing insta snapshots involves reading pending `.snap.new` files, evaluating the git diff to identify changes, and non-interactively accepting or rejecting them to ensure traceability without manual terminal intervention.

Can I manage cargo snapshot tests for linter and semantic crates non-interactively?

Yes, you can manage cargo snapshot tests for linter and semantic crates non-interactively. The skill automates the review of pending-snapshots across the workspace and verifies changes with standard git checks.

What is the best way to handle large numbers of insta snapshot changes during code review?

The best way to handle numerous insta snapshot changes is to automate the review process. This skill reads `.snap.new` files, accepts or rejects pending snapshots, and uses git diffs to verify results, reducing test maintenance bottlenecks.

Why do I need to use pending-snapshots for insta test automation?

You need to use pending-snapshots because the skill enforces their usage to identify changes between `.snap` and `.snap.new` files, enabling a structured, non-interactive review and verification process before accepting updates.