config-validator

Validate eslint.config.ts and tsconfig.json against documented architecture patterns.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/sovrium/sovrium --skill config-validator-sovrium
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config-validator
Source: https://github.com/sovrium/sovrium/tree/main/.claude/skills/validating-config
Command: npx skills add https://github.com/sovrium/sovrium --skill config-validator-sovrium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates eslint.config.ts and tsconfig.json against documented architecture patterns and infrastructure requirements. Checks ESLint plugin configurations, TypeScript strict mode, FP enforcement, layer boundaries, and alignment with docs/architecture/ and docs/infrastructure/.

Core Features & Use Cases

  • Read and compare config files against docs, report mismatches with remediation steps
  • Run lint and typecheck commands to verify enforcement
  • Check plugin versions and rule configurations

Quick Start

Run the validator to produce a configuration compliance report.

Frequently Asked Questions about config-validator

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

FAQPage Schema
How do I validate my ESLint and TypeScript configurations against architecture patterns?

Configuration validation compares your eslint.config.ts and tsconfig.json files against documented architecture and infrastructure requirements, reporting mismatches with remediation steps to ensure alignment with your project's standards.

Can I check if my ESLint rules and TypeScript settings match my team's documented standards?

Yes, the validator reads your config files, compares them against docs/architecture/ and docs/infrastructure/, and verifies plugin versions, strict mode, FP enforcement, and layer boundaries to identify deviations.

What should I validate in my ESLint and TypeScript configs before committing?

Validate plugin configurations, TypeScript strict mode settings, functional programming enforcement rules, layer boundary definitions, and plugin versions against your documented architecture patterns in your CI pipeline or locally.

How do I audit ESLint plugin versions and rule configurations automatically?

The validator runs lint and typecheck commands to verify enforcement, checks plugin versions and configurations against docs, and produces a compliance report identifying rule misalignments without modifying files.

Can I use configuration validation in CI pipelines to catch config drift?

Yes, run the validator in CI to detect when eslint.config.ts or tsconfig.json drift from documented requirements, catching misalignments early without manual code review.