check-xaml

Detect XAML syntax errors, missing namespaces, and broken resources in WPF projects.

Updated Aug 23, 2026

Search Tags:#validation #syntax #wpf #namespaces #bindings #xaml

Ready to run

npx skills add https://github.com/sekiya-sato/obsolete-cvnet10 --skill check-xaml

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check-xaml
Source: https://github.com/sekiya-sato/obsolete-cvnet10/tree/main/.agents/skills/check-xaml
Command: npx skills add https://github.com/sekiya-sato/obsolete-cvnet10 --skill check-xaml

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

XAML quality issues such as syntax errors, missing namespace declarations, and broken resource references slow down WPF UI development. This skill provides automated checks to catch these issues early and reduce debugging time.

Core Features & Use Cases

Syntax and tag-pairing checks: Detect mismatched tags and malformed attributes.
Namespace and resource validation: Ensure xmlns declarations exist and referenced resources/Converters are defined.
Binding verification (optional): Validate Binding paths against ViewModel properties when the ViewModel is accessible.
Use cases include CI checks to fail builds on XAML errors and local validation during UI implementation.

Quick Start

Open the XAML file you are editing and run the check to see reported syntax, namespace, and resource issues.

Frequently Asked Questions about check-xaml

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

FAQPage Schema

How do I check XAML files for syntax errors and missing namespaces in WPF?▼

You can validate XAML syntax and namespace declarations by running automated checks that detect mismatched tags, malformed attributes, and missing xmlns references in WPF projects, reporting these issues early during UI development.

What causes broken resource references and binding errors in XAML?▼

Broken resource references and binding errors in XAML are caused by missing namespace declarations, undefined converters, or invalid Binding paths that do not align with ViewModel properties. Automated checks identify these invalid references to prevent runtime failures.

Can I validate XAML binding paths against my ViewModel properties?▼

Yes, you can validate XAML binding paths against ViewModel properties when the ViewModel is accessible. The verification checks whether your Binding path references correctly align with the available ViewModel properties to catch binding issues early.

Does automated XAML validation work for WPF CI pipelines?▼

Yes, automated XAML validation works for WPF CI pipelines by running checks on newly created or edited XAML files. It catches syntax, namespace, and resource issues during continuous integration, allowing you to fail builds on detected XAML errors.

What is the best way to detect invalid converters and broken resources in XAML?▼

The best way to detect invalid converters and broken resources in XAML is to run namespace and resource validation that ensures referenced resources and converters are properly defined, preventing broken references from reaching runtime.