ln-511-code-quality-checker

Analyze implementation tasks for code quality and architectural compliance.

1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/bbsbot/mac-md-win --skill ln-511-code-quality-checker-bbsbot
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: ln-511-code-quality-checker
Source: https://github.com/bbsbot/mac-md-win/tree/main/.claude/skills/workflow/ln-511-code-quality-checker
Command: npx skills add https://github.com/bbsbot/mac-md-win --skill ln-511-code-quality-checker-bbsbot

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the assessment of code quality by applying quantitative metrics and architectural compliance checks, ensuring adherence to best practices and identifying potential issues before they escalate.

Core Features & Use Cases

  • Quantitative Code Scoring: Calculates a Code Quality Score based on metrics like cyclomatic complexity, function size, and nesting depth.
  • Architectural Validation: Validates architectural decisions against principles like DRY, KISS, and YAGNI, and checks for compliance with defined architectural layers and patterns.
  • Issue Identification & Reporting: Identifies and reports issues with standardized prefixes (SEC-, PERF-, MNT-, ARCH-, BP-, OPT-) and severity levels, providing actionable feedback.
  • Use Case: After a developer marks an implementation task as 'Done', this Skill can be invoked to automatically review the code for quality, performance, and architectural adherence, flagging any deviations from standards.

Quick Start

Use the ln-511-code-quality-checker skill to analyze the code for the 'user-authentication' story.

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 best practices?ā–¼

Automated code review for architectural compliance applies quantitative metrics and predefined rules to validate code against DRY, KISS, and YAGNI principles. It checks architectural layer integrity and reports deviations using standardized prefixes and severity levels.

How is code quality measured quantitatively during a code review?ā–¼

Code quality is measured quantitatively by calculating a Code Quality Score based on metrics like cyclomatic complexity, function size, and nesting depth. This score combines static code analysis and architectural validation to produce a comprehensive assessment.

What is the best way to check code for DRY, KISS, and YAGNI principle violations?ā–¼

The best way to check for DRY, KISS, and YAGNI violations is to run an automated architectural validation process that applies predefined rules to the codebase. It identifies principle deviations and reports them with standardized prefixes like ARCH- and BP-.

Can I use static code analysis to identify security and performance issues automatically?ā–¼

Yes, static code analysis identifies security and performance issues automatically by scanning the code against predefined rules. It flags vulnerabilities and inefficiencies using standardized prefixes like SEC- and PERF- with corresponding severity levels.

Does code quality scoring work for validating architectural layer integrity?ā–¼

Code quality scoring validates architectural layer integrity by checking code dependencies and structures against defined architectural patterns. It ensures compliance with established layers and reports any structural violations with the ARCH- prefix.

Why does my code review flag maintainability issues after marking an implementation task as done?ā–¼

Code review flags maintainability issues after task completion because automated analysis detects deviations from best practices using metrics like complexity and function size. It reports these issues with the MNT- prefix and severity levels to ensure standards adherence.