linear-issue-reviewer

Validate Linear sub-issue Done Criteria against code changes and comments.

18|3|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/buYoung/skills --skill linear-issue-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-issue-reviewer
Source: https://github.com/buYoung/skills/tree/main/skills/linear-issue-reviewer
Command: npx skills add https://github.com/buYoung/skills --skill linear-issue-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review completed Linear sub-issues: cross-validate Done Criteria, code changes, and worker comments to approve, request changes, or ask for clarification. Use when asked to review, validate, or QA done Linear issues.

Core Features & Use Cases

  • Validate Done Criteria across sub-issues against completion comments and code changes.
  • Cross-check target locations, file changes, and technical details to ensure scope accuracy.
  • Generate reviewer feedback and manage status transitions via the Linear API to keep the workflow consistent.
  • Use case: When a main issue has multiple sub-issues with strict acceptance criteria, this skill orchestrates the review and final approvals.

Quick Start

Provide the main Linear issue ID to trigger an end-to-end verification of all sub-issues and generate reviewer feedback.

Frequently Asked Questions about linear-issue-reviewer

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

FAQPage Schema
How do I automate code review for Linear sub-issues?

Automate code review for Linear sub-issues by providing a main issue ID to trigger end-to-end verification. The skill parses issue data, cross-checks code changes against Done Criteria, and extracts validation evidence from worker comments to generate reviewer feedback.

What is the best way to validate Done Criteria across multiple Linear sub-issues?

Validating Done Criteria across multiple Linear sub-issues involves cross-checking stated acceptance criteria against completion comments and actual code changes. This structured review process ensures scope accuracy by verifying target locations and technical details across all linked sub-issues.

How does automated issue review handle status transitions in Linear?

Automated issue review handles status transitions in Linear by generating reviewer feedback and managing issue states via the Linear API. This orchestration keeps the QA workflow consistent by guiding reviewers through verification, scope checks, and final approvals.

Can I cross-check code changes and worker comments for Linear issue QA?

Yes, you can cross-check code changes and worker comments for Linear issue QA. The process extracts evidence from completion comments and validates target file changes against the main issue's acceptance criteria to determine whether to approve or request changes.

Do I need a specific Linear issue structure to validate sub-issues?

You need a main Linear issue containing strict acceptance criteria and multiple linked sub-issues to validate sub-issues effectively. The review process relies on parsing this hierarchical structure to guide verification and final approvals across the sub-issues.

Why should I use automated issue review instead of manual QA for Linear sub-issues?

Automated issue review replaces manual QA for Linear sub-issues by systematically parsing issue data and cross-checking code changes against stated criteria. This structured approach prevents scope creep and ensures consistent verification across multiple sub-issues before final approval.