validator

Validate project structures against coding and documentation standards with JSON reports.

Updated Aug 23, 2026

Search Tags:#linting #documentation #compliance #quality #code #tools #validate

Ready to run

npx skills add https://github.com/ribatshepo/cc-auto-orchestrate --skill validator-ribatshepo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validator
Source: https://github.com/ribatshepo/cc-auto-orchestrate/tree/main/claude-code/skills/validator
Command: npx skills add https://github.com/ribatshepo/cc-auto-orchestrate --skill validator-ribatshepo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, jsonschema, and includes scripts (resource) components.

What problem does it solve?

Helps teams ensure code, docs, and project configurations meet defined standards by performing automated compliance checks.

Core Features & Use Cases

Automated file and structure checks: Enforces required files and proper project layout.
Pattern and schema validation: Detects forbidden patterns, validates against provided schemas when available.
Comprehensive reporting: Produces structured results with errors and warnings and guidance for remediation.
Use Case: Before merging changes, verify license, secret exposure, and documentation completeness to prevent compliance regressions.

Quick Start

Run the compliance checker against your project directory to generate a compliance report.

Frequently Asked Questions about validator

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

FAQPage Schema

How do I automate compliance checks for documentation completeness and project structure?▼

Automated compliance checks enforce required files and proper project layout by validating directory structures against established coding and documentation standards. The checker identifies missing files and reports findings with structured JSON output for remediation.

How does schema and pattern validation detect forbidden code patterns?▼

Schema and pattern validation detects forbidden code patterns by applying provided schemas to project files. It identifies non-compliant configurations and code quality issues, generating structured JSON results with errors and warnings to guide remediation.

Can I check for secret exposure and license issues before merging code changes?▼

Yes, you can check for secret exposure and license compliance before merging changes. The validator scans project repositories to prevent compliance regressions, verifying documentation completeness and detecting forbidden patterns within your codebase.

Do I need pyyaml and jsonschema dependencies to run compliance validation?▼

Yes, compliance validation requires pyyaml and jsonschema dependencies to perform schema validation and parse configuration files. These libraries enable the tool to apply provided schemas and detect forbidden patterns across project repositories.

What is the best way to validate project configurations against defined coding standards?▼

The best way to validate project configurations against defined coding standards is running an automated compliance checker across your project directory. It enforces required files, detects forbidden patterns, and outputs structured JSON reports with errors and warnings.

Why does compliance validation report errors and warnings instead of failing immediately?▼

Compliance validation reports errors and warnings instead of failing immediately to provide comprehensive reporting. This structured JSON output identifies all compliance issues across code quality, documentation completeness, and license checks, offering guidance for complete remediation.