linear-to-pr

Implements a Linear issue and opens a validated GitHub pull request with screenshots.

4|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/sethdavis512/iridium --skill linear-to-pr-sethdavis512
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-to-pr
Source: https://github.com/sethdavis512/iridium/tree/main/.claude/skills/linear-to-pr
Command: npx skills add https://github.com/sethdavis512/iridium --skill linear-to-pr-sethdavis512

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a Linear ticket into a reviewable pull request involves many manual steps: fetching issue context, branching correctly, implementing, running tests, capturing UI screenshots, and updating the issue status. This Skill automates that entire flow so nothing gets skipped. ## Core Features & Use Cases - End-to-end issue-to-PR workflow: Fetches the Linear issue and its comments, branches using Linear's suggested gitBranchName, implements the change, and opens the PR with gh. - Validation and e2e testing: Runs typecheck, lint, unit tests, and targeted Playwright specs, adding e2e coverage when new user-visible behavior ships. - Visual documentation: Captures themed, hydrated screenshots of changed surfaces via a visual inventory spec and links them in the PR body. - Use Case: You paste a linear.app issue URL like ABC-123 into the chat; the Skill implements the ticket, runs the notes e2e spec, attaches screenshots, opens the PR with Fixes ABC-123, and moves the issue to In Review. ## Quick Start Ask the assistant to work on a Linear issue by saying "work on ABC-123" or pasting the linear.app issue URL.

Frequently Asked Questions about linear-to-pr

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

FAQPage Schema
How do I turn a Linear issue into a GitHub pull request automatically?

Provide the issue identifier (e.g. ABC-123) or paste the linear.app URL. The workflow fetches the issue and comments, branches using Linear's gitBranchName, implements the change, runs validation and e2e tests, then opens the PR with gh and moves the issue to an in-review status.

How does the Linear GitHub integration auto-complete issues from a PR?

Including "Fixes ABC-123" in the PR body is a Linear magic word. With the GitHub integration enabled, the linked issue automatically moves to Done when the PR merges, so the workflow never sets Done manually.

What happens if no Linear MCP tools are available in the session?

The workflow asks you to paste the issue title and description manually, then proceeds with branching, implementation, validation, and PR creation. Only the Linear status updates and issue comments are skipped.

How are screenshots captured for UI changes in a pull request?

A Playwright visual inventory spec captures themed, hydrated, date-masked screenshots of affected surfaces into test-results/visual-inventory. For new surfaces, a temporary spec reuses the inventory helpers, and images are published via an image-hosting tool or Linear attachments.

When should this workflow not be used for Linear issues?

It is not for creating or triaging Linear issues, nor for reviewing or merging existing PRs. It also refuses to run prisma migrate or db push without explicit approval, and stops to ask for scope when the issue description is too vague.