ln-500-story-quality-gate

Orchestrate two-pass Story quality reviews across code, regression, and manual testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill orchestrates a two-pass Story review process: Pass 1 validates code quality, regression risk, and manual testing readiness; Pass 2 validates tests/coverage before marking the Story Done.

Core Features & Use Cases

  • Pass 1: run code quality checks, lint, and regression; create targeted fixes if issues are found; optionally create a test task.
  • Pass 2: verify test task status and coverage against AC; mark Story Done or generate necessary fixes.
  • Delegates to code-quality checkers and test planners, orchestrating the gating workflow.

Quick Start

When all implementation tasks are Done, run Pass 1 to validate readiness for tests; after tests pass, run Pass 2 to finalize the Story.

Frequently Asked Questions about ln-500-story-quality-gate

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

FAQPage Schema
How do I automate story quality review across code quality, regression, and testing?

Story quality review automation orchestrates two-pass checks: Pass 1 validates code quality, lint, and regression risk with fail-fast behavior; Pass 2 verifies test coverage against acceptance criteria before marking the Story Done. The Skill auto-discovers team configuration and delegates to code-quality checkers, linters, regression checkers, and test planners, creating targeted fix tasks as needed.

What's the difference between Pass 1 and Pass 2 in a story quality gate?

Pass 1 runs code quality checks, lint, and regression analysis, optionally creating a test task if issues surface. Pass 2 verifies test task status and coverage readiness, then marks the Story Done or generates necessary fixes. This two-pass structure ensures code validation precedes test verification.

Can I set up a quality gate that stops issues before test planning starts?

Yes. The Skill implements fail-fast behavior during Pass 1 by running code quality, lint, and regression checks upfront. If issues are detected, targeted fix or refactor tasks are created automatically, preventing progression to test planning until code quality gates pass.

How do I track story readiness to close in a quality gate workflow?

The Skill tracks Story status in Linear throughout the two-pass review. It auto-verifies or creates test tasks, then monitors completion before marking the Story Done. Status updates are maintained in Linear, providing end-to-end visibility from code validation through test verification.

Does a story quality gate work across multiple team configurations?

Yes. The Skill auto-discovers team and configuration settings, adapting the two-pass review process to your environment. It delegates tasks to configured code-quality checkers, linters, regression checkers, manual testers, and test planners without requiring manual setup for each team.

What happens if code quality or regression checks fail during story review?

The Skill creates targeted fix or refactor tasks automatically when issues are found, implementing fail-fast behavior to surface problems early. These tasks are tracked in Linear, ensuring issues are addressed before the Story progresses to test verification and closure.