Agent skill
dotnet-verify
This skill should be used when working with Verify snapshot tests in .NET projects. Use when updating verified snapshots after intentional code changes, accepting new snapshots, discovering verify tests, or troubleshooting snapshot mismatches. Trigger phrases include "verify tests", "update snapshots", "accept snapshots", "verified files", ".verified.txt".
Install this agent skill to your Project
npx add-skill https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-dotnet/skills/dotnet-verify
SKILL.md
.NET Verify Snapshot Testing
Manage Verify snapshot tests using the verify.tool dotnet local tool.
Discovery
To list all test files using Verify snapshots:
rg -l "Verifier\.Verify|UsesVerify|\.verified\." --type cs
To scope to a specific directory:
rg -l "Verifier\.Verify|UsesVerify|\.verified\." --type cs <path/to/test/directory>
Update Snapshots
To update snapshots after intentional code changes:
-
Build the solution:
bashdotnet build -p:WarningLevel=0 /clp:ErrorsOnly --verbosity minimal -
Run affected verify tests (they fail, generating
.received.files):bashdotnet test <test-project> --no-build --filter "FullyQualifiedName~<TestClass>" -v m -
Accept all new snapshots:
bashdotnet verify accept -yTo scope to a specific directory:
bashdotnet verify accept -y -w <path/to/test/directory> -
Re-run tests to confirm they pass:
bashdotnet test <test-project> --no-build --filter "FullyQualifiedName~<TestClass>" -v m
File Conventions
ClassName.MethodName.verified.txt— accepted snapshot (committed to git)ClassName.MethodName.received.txt— latest test output (not committed, gitignored)- Parameterized tests:
ClassName.MethodName_param=value.verified.txt
Quick Reference
| Command | Purpose |
|---|---|
dotnet verify accept -y |
Accept all pending snapshots |
dotnet verify accept -y -w <dir> |
Accept snapshots in specific directory |
rg -l "Verifier\.Verify|UsesVerify|\.verified\." --type cs |
List all test files using Verify |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
update-component-reference
This skill should be used when the user wants to add components (commands, agents, skills, hooks, or MCP servers) to the Component Reference section of the website.
version-bump
This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository.
spec-driven
Guide spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates between phases. Use when user wants structured feature planning or says "use spec-driven" or "follow the spec process".
nano-banana-prompting
This skill should be used when crafting prompts for Nano Banana Pro (Gemini image generation). Use when users want help writing image generation prompts, need guidance on prompt structure, or want to optimize their prompts for better results.
nano-banana
This skill should be used for Python scripting and Gemini image generation. Use when users ask to generate images, create AI art, edit images with AI, or run Python scripts with uv. Trigger phrases include "generate an image", "create a picture", "draw", "make an image of", "nano banana", or any image generation request.
structured-plan-mode
This skill should be used when planning and tracking complex feature implementations that require systematic task decomposition. Use this skill to break down large features into manageable, well-documented tasks with clear dependencies, action items, and success criteria. The skill provides a structured template and methodology for iterative planning and tracking throughout implementation.
Didn't find tool you were looking for?