ln-510-quality-coordinator

Orchestrate end-to-end code quality checks across LN components with storyId input.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/0xtaoist/taogate --skill ln-510-quality-coordinator-0xtaoist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-510-quality-coordinator
Source: https://github.com/0xtaoist/taogate/tree/main/ln-510-quality-coordinator
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-510-quality-coordinator-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multiple quality tasks across a software delivery workflow is complex and error-prone, and this skill centralizes orchestration to reduce drift and ensure consistent outcomes.

Core Features & Use Cases

  • Orchestrates ln-511 code-quality-checker, ln-512 tech-debt-cleaner, inline agent review, ln-513 regression-checker, and ln-514-test-log-analyzer.
  • Applies rigorous Phase 3 Criteria Validation, Phase 6 Linters, and final verdict computation per gate_levels.md to drive a compliant release.
  • Returns a consolidated quality_verdict plus aggregated results and stores a review history for traceability.

Quick Start

Trigger the quality coordinator with a storyId to start the full quality-gate workflow.

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 orchestrate end-to-end code quality checks for a software delivery workflow?

You can orchestrate code quality checks by triggering the coordinator with a storyId to run parallel agent reviews, regression checks, and linters across multiple components, producing a final quality verdict.

What is a quality gate in CI/CD and how does it aggregate agent reviews?

A quality gate aggregates parallel agent reviews, regression checks, log analysis, and criteria validation into a consolidated quality verdict ensuring compliant software releases without manual coordination drift.

How do I automate regression checks and tech debt cleanup together in a CI/CD pipeline?

Automate them by invoking a quality coordinator that sequentially triggers regression checking and tech debt cleaning agents, validating results against gate levels to compute a final release verdict.

Can I use a single storyId to trigger parallel code quality checks across multiple components?

Yes, passing a storyId triggers the full quality-gate workflow, coordinating tasks like inline agent reviews, regression checks, log analysis, and criteria validation across multiple LN components simultaneously.

What's the best way to calculate a final code quality verdict after running linters and criteria validation?

Calculate the final verdict by orchestrating linters, criteria validation, and regression checks, then aggregating the results per gate levels to drive a compliant release decision.

Why does my code quality coordination drift when running multiple agent reviews across different components?

Quality coordination drifts when multiple tasks are managed manually; centralizing orchestration ensures consistent outcomes by aggregating parallel agent reviews and validating criteria against predefined gate levels.