validate

Validate cc-initializer configuration components for presence, syntax, and reference integrity.

1|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/tygwan/AgenticREVIT --skill validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/tygwan/AgenticREVIT/tree/main/.claude/skills/validate
Command: npx skills add https://github.com/tygwan/AgenticREVIT --skill validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the integrity checks of cc-initializer configuration components such as settings.json, hooks, agents, skills, and documents, ensuring consistency and preventing misconfigurations that could disrupt automation pipelines.

Core Features & Use Cases

  • Configuration integrity checks: validates presence, syntax, and cross-references for settings.json, hooks, agents, and skills.
  • Audit reporting: generates concise validation results with actionable remediation guidance suitable for CI or manual reviews.
  • Use Case: before deploying a new initializer setup, run this skill to verify all components are correctly wired and ready for production.

Quick Start

Run the quick validation: /validate --quick Run the full validation: /validate --full Generate a detailed report: /validate --report

Frequently Asked Questions about validate

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

FAQPage Schema
How do I validate cc-initializer configuration before deployment?

Configuration validation checks settings.json, hooks, agents, and skills for presence, syntax errors, and broken references. Run `/validate --full` to perform comprehensive integrity checks across all components and identify misconfigurations before deploying your initializer setup.

What does cc-initializer validation check for?

Validation enforces configuration integrity by verifying presence of required settings.json and component files, confirming valid syntax across hooks, agents, and skills, and checking that cross-references between components are correctly wired and resolvable.

Can I get a detailed report of validation errors?

Yes. Run `/validate --report` to generate a detailed audit report with concise validation results and actionable remediation guidance. This output is suitable for CI pipelines or manual review to resolve configuration issues.

What's the fastest way to run a validation check?

Use `/validate --quick` for a rapid validation pass. This performs essential integrity checks without the full depth, ideal for quick verification during development before running the complete `/validate --full` workflow.

Do I need to set up anything before validating my initializer configuration?

No special setup required. Validation works directly on your existing settings.json, hooks, agents, skills, and documents. Ensure these configuration components are present in your project directory, then run validation commands.

What happens if validation finds broken references between components?

Validation identifies broken cross-references between settings.json, hooks, agents, and skills, then provides actionable remediation guidance in the audit report. Fix the issues and re-run validation to confirm all components are correctly wired.