plugins/handbook-dotnet/skills/dotnet-verify/SKILL.md
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".
npx skillsauth add nikiforovall/claude-code-rules dotnet-verifyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Manage Verify snapshot tests using the verify.tool dotnet local tool.
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>
To update snapshots after intentional code changes:
Build the solution:
dotnet build -p:WarningLevel=0 /clp:ErrorsOnly --verbosity minimal
Run affected verify tests (they fail, generating .received. files):
dotnet test <test-project> --no-build --filter "FullyQualifiedName~<TestClass>" -v m
Accept all new snapshots:
dotnet verify accept -y
To scope to a specific directory:
dotnet verify accept -y -w <path/to/test/directory>
Re-run tests to confirm they pass:
dotnet test <test-project> --no-build --filter "FullyQualifiedName~<TestClass>" -v m
ClassName.MethodName.verified.txt — accepted snapshot (committed to git)ClassName.MethodName.received.txt — latest test output (not committed, gitignored)ClassName.MethodName_param=value.verified.txt| 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 |
development
Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.
tools
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
tools
--- name: reflect description: Analyze a Claude Code session for "wrong-turn" moments (corrections, retries, waste, reversals, dead-ends) and produce an interactive HTML dashboard with copy-able recommendations (CLAUDE.md rules, docs, scripts, hooks, memory entries, sub-skills, etc.) that would help future agents reach the goal faster. Defaults to reflecting on the current in-context session; optionally accepts a session ID or JSONL path. Use when the user invokes /reflect or asks to learn from
tools
--- name: reflect-tree description: Visualize a Claude Code session as a quest/skill tree — a navigable SVG graph where nodes are turns and edges show flow, with distinct visual encoding for normal flow, dead-ends, corrections, retries, reversals, and backtracking. Sibling to /reflect (which produces an incidents+recommendations dashboard); this one shows the journey itself. Defaults to the current in-context session; optionally accepts a session ID or JSONL path. Use when the user invokes /refl