verification-protocol

Verify .NET MAUI and Comet app behavior on real devices against reference code and screenshots.

209|27|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dotnet/maui-labs --skill verification-protocol-dotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-protocol
Source: https://github.com/dotnet/maui-labs/tree/main/src/Comet/.squad/skills/verification-protocol
Command: npx skills add https://github.com/dotnet/maui-labs --skill verification-protocol-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents teams from marking work as done when changes only compile, deploy stale binaries, or fail in real UI behavior—ensuring verification is owned, repeatable, and grounded in reference evidence.

Core Features & Use Cases

  • Own Your Dependencies: Diagnose and fix broken tools/configuration in the verification chain instead of reporting as blocked.
  • Verify Against Reference: Compare actual results to the original app code and reference screenshots, not “looks right” guesses.
  • Verify the Specific Change: Exercise the exact behavior your task modified (navigation, inputs, crashes, features) so reports are complete.
  • Confirm Fresh Binary: Clean/rebuild and validate the on-device binary freshness before accepting inspection/interactions.
  • Verification Levels L1–L4 (and L5 as applicable): Build, deploy, DevFlow inspection, interactive UI exercise, with an additional feature-focused checklist when in scope.

Quick Start

Use verification-protocol to validate any task that touches UI, pages, navigation, services, or app behavior by running the full L1–L4 device and DevFlow workflow and reporting results with the required template.

Frequently Asked Questions about verification-protocol

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

FAQPage Schema
How do I verify .NET MAUI UI changes on real devices?

Verifying .NET MAUI changes on real devices requires a clean rebuild, fresh binary deployment, DevFlow visual tree inspection, screenshot comparison against reference code, and interactive UI exercise to validate exact modified behaviors.

What is the best way to test Comet app navigation end-to-end?

Testing Comet app navigation end-to-end involves owning your dependencies, confirming fresh binary deployment, using DevFlow to inspect the visual tree, and interactively exercising the exact navigation paths modified by your task against reference screenshots.

Why does DevFlow fail during MAUI device testing and how do I fix it?

DevFlow failures during MAUI device testing often stem from broken tools or configuration issues; you must diagnose and fix the verification chain dependencies directly instead of reporting the task as blocked to ensure accurate end-to-end validation.

Does my .NET MAUI verification process need reference screenshots?

Yes, .NET MAUI verification requires reference screenshots to compare actual on-device results against original app code, preventing teams from accepting changes that merely compile but fail in real UI behavior due to stale binaries.

How do I confirm a fresh binary is deployed before MAUI UI testing?

To confirm a fresh binary is deployed before MAUI UI testing, perform a clean rebuild, validate the on-device binary freshness, and ensure stale binaries are completely removed before accepting DevFlow inspection or interactive UI interactions.