ln-623-code-principles-auditor

Audit code for DRY, KISS/YAGNI, error handling, and Dependency Injection violations.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-623-code-principles-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-623-code-principles-auditor
Source: https://github.com/dorrio/sorteo-app-generator/tree/main/.agent/skills/ln-623-code-principles-auditor
Command: npx skills add https://github.com/dorrio/sorteo-app-generator --skill ln-623-code-principles-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies violations of fundamental software development principles, ensuring code quality and maintainability.

Core Features & Use Cases

  • DRY Principle Check: Detects 10 types of duplication.
  • KISS/YAGNI Adherence: Assesses code simplicity and necessity.
  • Error Handling Audit: Reviews the robustness of error management.
  • DI Pattern Verification: Checks for correct implementation of Dependency Injection.
  • Use Case: A developer can use this skill to automatically audit a new feature's code against best practices before merging, catching potential issues early.

Quick Start

Run the code principles auditor skill on the current project files.

Frequently Asked Questions about ln-623-code-principles-auditor

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

FAQPage Schema
How do I audit my code for DRY principle violations?

Auditing code for DRY violations involves scanning project files to detect 10 types of duplication. This tool returns findings with severity, location, and pattern signatures for code quality assessment.

Can I check if my code follows KISS and YAGNI principles automatically?

Checking code for KISS and YAGNI adherence assesses code simplicity and necessity. The tool returns findings with severity and effort estimates to highlight potential over-engineering.

What is the best way to review error handling and dependency injection patterns?

Reviewing error handling and dependency injection patterns requires running an automated code audit. It checks robust error management and correct DI implementation, returning locations and severity for deviations.

Does the code audit report show where the principle violations are located?

Yes, the code audit report shows where principle violations are located. Each finding includes severity, location, effort to fix, and a pattern signature for comprehensive code quality assessment.

When do I need to run a software development principles audit?

Run a software development principles audit before merging a new feature to catch issues early. This ensures codebase quality and maintainability by checking for DRY, KISS, and error handling deviations.