verify

Automate end-to-end runtime verification across extension, CLI, MCP, TUI, and workflow surfaces.

5|1|Updated Dec 14, 2025

Search Tags:#workflow #testing #verification #runtime #mcp #extension #ci

Ready to run

npx skills add https://github.com/joshsmithxrm/power-platform-developer-suite --skill verify-joshsmithxrm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/joshsmithxrm/power-platform-developer-suite/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/joshsmithxrm/power-platform-developer-suite --skill verify-joshsmithxrm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifying that newly implemented features across extension, CLI, MCP, TUI, and workflow actually run correctly in runtime environments, reducing regressions and post-release surprises.

Core Features & Use Cases

End-to-end runtime verification across all surfaces after code changes
Structured verification checks during CI, manual testing, and post-deploy validation
Clear, actionable reporting of failures and guardrails to prevent regressions

Quick Start

Run the verify workflow after code changes to validate runtime behavior across all surfaces.

Frequently Asked Questions about verify

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

FAQPage Schema

How do I automate runtime verification across Power Platform extension and workflow surfaces?▼

Runtime verification is automated across Power Platform by running scripted checks that validate toolchain interactions, outputs, and error handling across extension, CLI, MCP, TUI, and workflow surfaces to ensure components behave correctly.

What is the best way to validate newly implemented features in a CI pipeline to prevent regressions?▼

Validating newly implemented features in CI involves applying structured verification checks that test runtime environments, providing clear reporting of failures and guardrails to prevent post-release regressions and surprises.

Can I use runtime verification for manual testing and post-deploy validation on the Power Platform?▼

Runtime verification can be applied during manual testing and post-deploy validation to confirm that newly implemented features across all surfaces run correctly in their actual runtime environments.

Does runtime verification work with MCP, CLI, and TUI toolchain interactions?▼

Runtime verification works with MCP, CLI, and TUI toolchain interactions by applying scripted checks that validate component behavior, outputs, and error handling across these multiple surfaces.

Why does my newly implemented feature pass local checks but fail in runtime environments?▼

Features may fail in runtime environments due to unverified toolchain interactions across surfaces, which end-to-end runtime verification addresses by applying structured checks during post-implementation validation.

When do I need end-to-end runtime verification for my code changes?▼

End-to-end runtime verification is needed after code changes to ensure that newly implemented features across extension, CLI, MCP, TUI, and workflow surfaces actually run correctly in runtime environments.