ln-501-code-quality-checker

Analyze Done Linear tasks for code-quality violations and post structured issue reports.

534|73|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-501-code-quality-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-501-code-quality-checker
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-501-code-quality-checker
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-501-code-quality-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill analyzes Done implementation tasks for code-quality issues, including DRY/KISS/YAGNI violations, architecture violations, and hardcoded patterns, and reports findings without changing Linear or kanban states.

Core Features & Use Cases

  • Evaluate code for DRY violations, architectural boundary breaches, and hard-coded patterns.
  • Produce a structured report of issues with location, severity, and remediation recommendations.
  • Post Linear comments detailing findings to inform next actions.

Quick Start

Run after implementation tasks are completed to surface actionable quality issues before proceeding to review.

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

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

FAQPage Schema
How do I detect code quality violations like DRY and KISS violations in my implementation?

Code quality analysis identifies DRY, KISS, and YAGNI violations by scanning implementation code and documentation for duplication, over-engineering, hardcoding, and architectural boundary breaches. This Skill examines Done tasks in Linear, aggregates affected files and recent commits, and produces a structured report with severity and remediation guidance.

Can I check for architecture violations and layering issues in my codebase?

Yes. The analysis detects improper layering, architecture boundary violations, and hardcoded patterns across your implementation. It reviews code and documentation loaded from Linear Done tasks, flags violations by category and severity, and posts findings as Linear comments to inform next steps.

When should I run code quality checks in my development workflow?

Run this analysis after implementation tasks reach Done status and before code review. It surfaces actionable quality issues early, enabling you to address DRY/KISS violations, architectural problems, and missing API documentation before the review phase progresses.

What's included in the code quality report?

The report delivers a verdict (PASS or ISSUES_FOUND) with a structured issue list containing category, severity, file location, and specific remediation recommendations. Results post to Linear as comments without modifying task statuses or creating new tasks.

Does this work with Linear and recent commit history?

Yes. The Skill loads Done implementation tasks and Story descriptions from Linear, aggregates affected files and recent commits, and analyzes both code and documentation. It posts findings directly to Linear comments for visibility across your workflow.