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".
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 |
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.
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.
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".
Review changed code for reuse, quality, and efficiency using three parallel disposable subagents. This skill should be used when the user says "review", "simplify", "code review", or wants a one-shot code review without persistent reviewers.
Review changed code for reuse, quality, and efficiency using a team of persistent named reviewers. This skill should be used when the user says "team review", "review with team", or wants parallel code review with persistent team members for follow-up questions. Similar to /subagent-review but reviewers persist after review.
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".
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.