principles-validate

Identify Python code violating SSOT, DRY, naming, and structural principles.

31|5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/NSEvteev/FullSpec --skill principles-validate-nsevteev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: principles-validate
Source: https://github.com/NSEvteev/FullSpec/tree/main/.claude/skills/principles-validate
Command: npx skills add https://github.com/NSEvteev/FullSpec --skill principles-validate-nsevteev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate Python code against the project's core principles (SSOT, DRY, naming, and structure) to improve consistency and maintainability.

Core Features & Use Cases

  • Validates code against SSOT, DRY, naming conventions, and structural rules.
  • Supports repository-wide scans or targeted file checks for code reviews, refactoring, and post-implementation validation.
  • Generates structured reports to guide fixes and track compliance over time.

Quick Start

Run the /principles-validate command on a target path to validate Python code against the project's principles.

Frequently Asked Questions about principles-validate

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

FAQPage Schema
How do I check Python code for DRY and SSOT principle violations?

To check Python code for DRY and SSOT principle violations, run a validation command that scans target paths and identifies structural inconsistencies. It outputs a structured report detailing where code fails to meet these maintainability standards.

Can I automate naming convention checks during a Python code review?

Yes, you can automate naming convention checks during a Python code review by running a principles validation scan on targeted files. This identifies naming inconsistencies and generates a report to guide necessary fixes.

What is the best way to validate project structure across a Python repository?

The best way to validate project structure across a Python repository is to perform a repository-wide scan for principle violations. This evaluates the codebase against structural rules to produce a comprehensive compliance report.

How do I generate a report for refactoring Python code based on code quality?

To generate a report for refactoring Python code based on code quality, run a principles validation check on the target path. It outputs a structured compliance report highlighting SSOT, DRY, and naming issues to guide fixes.

Does this principles validation support targeted file checks for post-implementation review?

Yes, this principles validation supports targeted file checks for post-implementation review. You can run the command on specific files to verify SSOT, DRY, and naming compliance instead of scanning the entire Python repository.