dotnet-verify
The dotnet-verify skill manages Verify snapshot tests in .NET projects using the verify.tool dotnet local tool. Use it to discover snapshot test files, update verified snapshots after intentional code changes, accept new snapshots, and troubleshoot snapshot mismatches by comparing received output against committed verified files.
git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules /tmp/dotnet-verify && cp -r /tmp/dotnet-verify/plugins/handbook-dotnet/skills/dotnet-verify ~/.claude/skills/dotnet-verifySKILL.md
# .NET Verify Snapshot Testing Manage [Verify](https://github.com/VerifyTests/Verify) snapshot tests using the `verify.tool` dotnet local tool. ## Discovery To list all test files using Verify snapshots: ```bash rg -l "Verifier\.Verify|UsesVerify|\.verified\." --type cs ``` To scope to a specific directory: ```bash rg -l "Verifier\.Verify|UsesVerify|\.verified\." --type cs <path/to/test/directory> ``` ## Update Snapshots To update snapshots after intentional code changes: 1. Build the solution: ```bash dotnet build -p:WarningLevel=0 /clp:ErrorsOnly --verbosity minimal ``` 2. Run affected verify tests (they fail, generating `.received.` files): ```bash dotnet test <test-project> --no-build --filter "FullyQualifiedName~<TestClass>" -v m ``` 3. Accept all new snapshots: ```bash dotnet verify accept -y ``` To scope to a specific directory: ```bash dotnet verify accept -y -w <path/to/test/directory> ``` 4. Re-run tests to confirm they pass: ```bash dotnet 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 |
Analyze a task and produce an Architecture Decision Record with implementation steps.
Generate a .NET code coverage report scoped to files changed in the current branch. Runs tests with coverage collection and produces filtered HTML reports.
This skill should be used when investigating .NET project dependencies, understanding why packages are included, listing references, or auditing for outdated/vulnerable packages.
Run script-like CSharp programs using dotnet run file.cs. Use this skill when users want to execute CSharp code directly, write one-liner scripts via stdin, or learn about run file directives.
>
This skill should be used when the user wants to manage Git worktrees - creating worktrees from local or remote branches, listing active worktrees with details, deleting worktrees, or switching between worktrees. Ideal for working on multiple branches simultaneously without stashing changes.
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.
This skill should be used when users want to discover, browse, or audit cc-handbook marketplace plugins. Shows all available plugins with installation status, versions, and component breakdown (skills, agents, commands, MCP/LSP servers, hooks). Trigger phrases include "discover plugins", "list handbook plugins", "what plugins are available", "browse marketplace".