ln-511-code-quality-checker

Calculate code quality scores and validate DRY, KISS, YAGNI compliance.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/mcauduro0/Macro_Trading --skill ln-511-code-quality-checker-mcauduro0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-511-code-quality-checker
Source: https://github.com/mcauduro0/Macro_Trading/tree/main/.claude/skills/ln-511-code-quality-checker
Command: npx skills add https://github.com/mcauduro0/Macro_Trading --skill ln-511-code-quality-checker-mcauduro0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the rigorous assessment of code quality, ensuring adherence to best practices, architectural standards, and performance benchmarks, thereby reducing technical debt and improving maintainability.

Core Features & Use Cases

  • Quantitative Code Scoring: Calculates a Code Quality Score based on metrics like cyclomatic complexity, function/file size, and nesting depth.
  • Compliance Validation: Checks for DRY/KISS/YAGNI violations, architectural boundary adherence, and security vulnerabilities using predefined rules and MCP Ref documentation.
  • Use Case: Before merging a new feature, this Skill can be invoked to analyze the implemented code, providing a detailed report on potential issues and a quality score, ensuring only high-quality code is integrated.

Quick Start

Analyze the code quality of the latest commit using the ln-511-code-quality-checker skill.

Frequently Asked Questions about ln-511-code-quality-checker

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

FAQPage Schema
How do I automate code review for architectural compliance and technical debt?

Static analysis validates code against architectural boundaries, DRY, KISS, and YAGNI principles, calculating a quantitative quality score based on cyclomatic complexity and nesting depth to flag technical debt using specific issue prefixes.

What metrics are used to calculate a quantitative code quality score?

A code quality score is calculated using static analysis metrics including cyclomatic complexity, function and file size, and nesting depth, providing a final score interpretation to assess overall maintainability.

How do I check my code for DRY, KISS, and YAGNI violations before merging?

Automated compliance validation checks your code for DRY, KISS, and YAGNI violations, reporting issues with specific prefixes like MNT- and ARCH- to ensure only high-quality code is integrated into the main branch.

Does static analysis detect security vulnerabilities and performance issues?

Static analysis detects security vulnerabilities and performance issues by validating code against predefined rules, reporting findings with specific prefixes such as SEC- and PERF- alongside the final code quality score.

Can I use static analysis to enforce architectural boundary adherence in my codebase?

Yes, static analysis enforces architectural boundary adherence by validating code against architectural principles using MCP Ref documentation, reporting any architectural compliance violations with the ARCH- prefix.