ln-510-quality-coordinator

Analyze code quality, clean tech debt, and run regression tests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of deep-diving into code quality, identifying and fixing technical debt, and ensuring that changes do not introduce regressions, thereby streamlining the review process.

Core Features & Use Cases

  • Code Quality Analysis: Detects code smells, architectural alignment, and unexpected side-effects.
  • Automated Tech Debt Cleanup: Fixes issues like unused imports and dead code.
  • Validation & Linting: Ensures adherence to project standards and criteria.
  • Regression Testing: Verifies that existing functionality remains intact.
  • Use Case: After a developer completes a feature, this Skill can be invoked to automatically check the code for quality issues, fix minor problems, and run tests before it's presented for final review.

Quick Start

Run a quality analysis on the recent code changes and report any issues found.

Frequently Asked Questions about ln-510-quality-coordinator

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

FAQPage Schema
How do I automate code quality analysis and tech debt cleanup after finishing a feature?

Automated code quality analysis detects code smells, architectural misalignment, and side-effects, while tech debt cleanup removes unused imports and dead code to streamline your review process.

Can I run regression testing and linting automatically before final code review?

Yes, regression testing verifies existing functionality remains intact and linting validates changes against project standards, ensuring stability before presenting code for final review.

What is the best way to validate code changes against architectural standards and acceptance criteria?

Validating changes against architectural standards involves deep-dive code quality analysis, checking for unexpected side-effects, and reporting a quality verdict to the Quality Gate for final decision.

Does code review automation work for identifying technical debt and dead code in software development stories?

Code review automation coordinates deep-dive analysis for software development stories, identifying technical debt and fixing issues like dead code before submitting changes to the Quality Gate.

How do I ensure code stability when fixing technical debt and removing unused imports?

Ensuring code stability requires running regression checks and test suites after tech debt cleanup, verifying that automated fixes for unused imports and dead code do not introduce regressions.

When should I not use automated linting and regression checks for code quality?

Automated linting and regression checks are less suitable for early prototyping phases where architectural standards are undefined, as the quality verdict validates changes against established project criteria.