validate-all

Run all validators to verify X-DEEP architecture health and detect drift.

Updated Apr 14, 2026

Search Tags:#architecture #validation #drift #validators #ci #project-checks

Ready to run

npx skills add https://github.com/ysgdepaula/x-deep-os --skill validate-all-ysgdepaula

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validate-all
Source: https://github.com/ysgdepaula/x-deep-os/tree/main/.claude/skills/validate-all
Command: npx skills add https://github.com/ysgdepaula/x-deep-os --skill validate-all-ysgdepaula

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Single entry point to verify the health of the X-DEEP architecture by running core validators (state, templates, skills) and project checks, ensuring configuration integrity and drift detection.

Core Features & Use Cases

Core validators: verify state.json structure, template parsing, and skill frontmatter validity.
Project checks: run lint/tests for relevant projects when related files change to catch integration issues.
Use case: Teams can validate the architecture before commits or PRs to guarantee consistency across the system.

Quick Start

Run the /validate-all command to verify the X-DEEP architecture health and report results.

Frequently Asked Questions about validate-all

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

FAQPage Schema

How do I detect architecture drift across multiple projects?▼

To detect architecture drift across projects, run all validators to verify state.json structure, template parsing, and skill frontmatter validity. This single entry point checks configuration integrity and reports project-level drift detection for relevant components.

When do I need to run architecture validators?▼

You need to run architecture validators after making changes to core folders like .agent or .claude/skills, or on demand before commits and PRs. Running validators ensures configuration integrity and catches integration issues across the system.

How to validate skill frontmatter and template parsing in CI?▼

Run the validate-all command in your CI pipeline to validate skill frontmatter and template parsing. It acts as a single entry point to verify X-DEEP architecture health, ensuring state.json structure and reporting project-level checks.

Can I run project-level checks for lint and tests automatically?▼

Yes, you can run project-level checks for lint and tests automatically when related files change. The validator runs these checks to catch integration issues and verify overall configuration integrity across relevant projects.

What is the best way to verify X-DEEP architecture health consistently?▼

The best way to verify X-DEEP architecture health consistently is to run a unified validation command before commits. It executes core validators for state, templates, and skills, guaranteeing system consistency and detecting drift.

Why does my state.json structure validation fail after core folder changes?▼

State.json structure validation may fail after core folder changes due to configuration drift. Running all validators detects this drift, verifying state.json structure, template parsing, and skill frontmatter validity to restore architecture health.