verification-loop

Execute a 7-phase .NET verification pipeline with structured PASS/WARN/FAIL reporting.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill verification-loop-trossitec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-loop
Source: https://github.com/Trossitec/dotnet-claude-kit/tree/main/skills/verification-loop
Command: npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill verification-loop-trossitec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or risky .NET changes from reaching integration by enforcing a repeatable verification pipeline that reports clear PASS/FAIL outcomes across build, diagnostics, anti-patterns, tests, security, formatting, and diff review.

Core Features & Use Cases

  • 7-phase verification pipeline: Runs an ordered set of checks that short-circuits on critical failures to save time.
  • NEW-warning enforcement: Flags only newly introduced warnings by comparing against a baseline, reducing noise.
  • Actionable structured reporting: Produces an explicit phase-by-phase report plus follow-up action items, so teams can fix issues quickly.
  • Practical CI/pre-PR gating: Supports common workflows like “verify before merge” and “is this ready?” for feature-complete and refactor PRs.

Quick Start

Run the full 7-phase verification loop by asking Claude to verify your change with a pre-PR check intent (for example, “run verification pipeline check everything and generate the structured report”).

Frequently Asked Questions about verification-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a pre-PR quality gate check for .NET changes?

A .NET verification pipeline prevents broken or risky changes from reaching integration by enforcing a repeatable process that reports clear PASS/FAIL outcomes across build, tests, security, and formatting checks.

How does baseline comparison work for detecting new warnings in .NET builds?

Baseline comparison for new warnings flags only newly introduced warnings by comparing current build diagnostics against a stored baseline, reducing noise from pre-existing issues.

Can I enforce formatting compliance and security scanning before merging .NET pull requests?

You can enforce formatting compliance and security scanning before merging by running the verification pipeline, which short-circuits on critical failures and generates a structured PASS/WARN/FAIL report.

What is the best way to automate anti-pattern detection in a .NET codebase?

Automate anti-pattern detection by including it as a dedicated phase in the .NET verification pipeline, which runs checks iteratively and provides actionable remediation steps for any detected violations.

Does the .NET verification pipeline short-circuit on build failures?

The verification pipeline applies strict phase short-circuiting on critical failures, meaning subsequent phases are skipped if a critical build or test failure occurs to save time.

Why do I need a structured PASS/WARN/FAIL report for .NET change validation?

A structured PASS/WARN/FAIL report provides explicit phase-by-phase outcomes and follow-up action items, enabling teams to quickly fix issues during iterative fix-and-retry loops for change validation.