verifylisted
Install: claude install-skill lamuniercosta/dotnet-agent-harness
# Verify — Verification Pipeline
Adapted from [codewithmukesh/dotnet-claude-kit](https://github.com/codewithmukesh/dotnet-claude-kit) (MIT). The upstream Roslyn MCP phases are replaced with standard `dotnet` tooling plus this harness's gate scripts, so the skill has **no MCP dependency and no third-party service**.
## What it is
A sequential pipeline that answers one question: **"Is this code ready for review?"** Each phase reports PASS/WARN/FAIL. Critical failures (build, tests) short-circuit — later phases are meaningless on broken code.
This is the ad-hoc runner. It wraps the same scripts the gated pipeline uses, so readiness can be checked at any time without running the full `/refactor` → `/architect` sequence. It **complements** the gates; it does not replace them. "It looks fine" is not a result — a table of statuses is.
| Phase | Tool | Critical |
|---|---|---|
| 1. Build | `dotnet build` | Yes |
| 2. Analyzers | `./scripts/run-roslyn-analyzers.ps1` | Yes |
| 3. Complexity | `./scripts/run-cyclomatic-complexity.ps1` | Yes |
| 4. InspectCode | `./scripts/run-jetbrains-inspectcode.ps1` | Yes |
| 5. Tests | `dotnet test` | Yes |
| 6. Property tests | `./scripts/run-property-tests.ps1` | FAIL on counterexample |
| 7. Security | `./scripts/run-vulnerable-packages.ps1` + secret/injection review | FAIL on any vulnerable package |
| 8. Format | `dotnet format --verify-no-changes` | No |
| 9. Mutation | `dotnet stryker` (scoped: `--mutate "**/File.cs"`) | FAIL below thres