code-style-validator

Automated code-style validation uses AST analysis to detect naming, formatting, and structural inconsistencies without manual review. This Skill analyzes your codebase, reports violations with precise line and column locations, and outputs results in JSON format for integration into pre-commit hooks, code reviews, and CI/CD pipelines.

Yes. AST-based validation runs in pre-commit hooks to catch style violations before code reaches your repository. Configurable rules check naming conventions, formatting, and structure across TypeScript, JavaScript, and Python, blocking commits that violate your defined standards.

AST analysis parses code into a syntax tree, understanding structure and context with precision. This approach detects semantic violations—incorrect naming patterns, structural inconsistencies—that regex cannot catch, enabling accurate rule enforcement across complex codebases.

Language-specific AST parsers analyze TypeScript, JavaScript, and Python independently, but configuration occurs once. Define your naming conventions and formatting rules centrally; the Skill applies them appropriately to each language during validation.

The Skill outputs structured JSON containing file paths, validation status, issues with locations, and summaries. This schema feeds directly into CI/CD systems, failing builds when violations are detected and reporting detailed results for code review workflows.

Violations are reported with file name, line number, column position, and issue description in JSON output. This precise location data enables developers to fix violations quickly and integrates seamlessly into editors, review tools, and automated workflows.