Ln 511 Code Quality Checker

What it does

The Ln 511 Code Quality Checker analyzes backend code to identify potential quality issues and improve maintainability. It calculates a quantitative "Code Quality Score" based on metrics like cyclomatic complexity, function size, and nesting depth, alongside validations against external references (MCP Ref). The tool flags violations of best practices such as DRY/KISS/YAGNI and checks for security vulnerabilities and performance bottlenecks.

When to use it

• Reviewing implementation tasks marked as "In Progress" or "To Review" on a Kanban board.
• Assessing the quality of code related to a specific story (identified by storyId).
• Identifying areas where code can be refactored for better performance and maintainability.
• Ensuring adherence to coding standards and best practices within a backend project.

Key capabilities

• Calculates a Code Quality Score based on defined metrics and issue penalties.
• Performs MCP Ref validation, checking for optimality, best practices, and performance issues.
• Identifies violations of DRY (Don't Repeat Yourself), KISS (Keep It Simple, Stupid), and YAGNI (You Ain’t Gonna Need It) principles.
• Checks for security vulnerabilities and performance bottlenecks.
• Provides a structured list of identified issues with severity levels (high, medium, low).

Example prompts

• "Analyze the code quality for storyId 12345."
• "Check the code quality of the 'user authentication' feature on the 'development' branch."
• "What are the potential maintainability issues in this code?"

Tips & gotchas

• The skill requires a storyId as input.
• Ensure that shared/references/mcp_tool_preferences.md and shared/references/mcp_integration_patterns.md are accessible for optimal results, particularly when using hex-graph evidence.
• The tool does not edit the Linear or Kanban board; it only provides analysis and issue lists.