Story Quality Gate (Linear Integration) FAQs

Question 1

Does it integrate with other developer tools?

Accepted Answer

It is specifically designed to work within the Claude Code ecosystem, coordinating with sub-skills for code quality (ln-341), regression (ln-342), manual testing (ln-343), and test planning (ln-350).

Question 2

How does it handle failures during the quality check?

Accepted Answer

The skill uses a fail-fast approach; if any check fails, it automatically creates a specific remediation task (e.g., refactor, lint-fix, bug-fix) in Linear and stops the process to prevent low-quality code from advancing.

Question 3

Can I manually trigger a specific validation pass?

Accepted Answer

Yes, while the skill typically auto-detects the required pass based on Linear task status, you can provide an explicit 'pass' parameter to force either the initial quality check or the final test verification.

Question 4

Does this skill require specific project documentation?

Accepted Answer

Yes, it utilizes your project's tech_stack.md file to identify relevant linters and architectural rules to enforce during the validation process.

Question 5

What is the difference between Pass 1 and Pass 2 reviews?

Accepted Answer

Pass 1 focuses on immediate code health, including linting, regression, and manual testing to identify blockers early. Pass 2 occurs after testing tasks are complete to verify coverage, priority limits, and finalize the Story in the management tool.

Story Quality Gate (Linear Integration)

Story Quality Gate (Linear Integration)

Key Features

Use Cases

Key Features

Use Cases