linear-ticket-work

Executes a Linear engineering ticket through to an atomic Graphite pull request.

Updated May 18, 2025
One-click install
npx skills add https://github.com/nthpaul/dotfiles --skill linear-ticket-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-ticket-work
Source: https://github.com/nthpaul/dotfiles/tree/main/cursor/.cursor/skills/linear-ticket-work
Command: npx skills add https://github.com/nthpaul/dotfiles --skill linear-ticket-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the risk and friction of taking an engineering ticket from Linear through implementation, local verification, and an atomic Graphite PR with correct scope and sequencing.

Core Features & Use Cases

  • Dependency-aware ticket execution: Verifies whether prerequisite tickets or PRs are already implemented before starting and blocks when evidence is missing.
  • Repo-guided, scope-limited changes: Loads repo authoring guidance (AGENTS.md, CLAUDE.md, and relevant BUGBOT docs) and constrains work to the ticketed scope unless correctness requires expansion.
  • Local validation before PR: Runs the repo-specific lint/typecheck/format commands (and targeted tests) until all required checks pass, then submits via Graphite and links back to Linear.

Quick Start

Use the linear ticket workflow for issue <ISSUE_ID> by starting the ticket, implementing only the scoped changes, running the required local validations, then creating and submitting the Graphite PR and posting a concise follow-up to the issue.

Frequently Asked Questions about linear-ticket-work

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

FAQPage Schema
How do I create an atomic pull request for a Linear ticket using Graphite?

Dependency gating checks whether prerequisite tickets or PRs are already implemented before starting work, blocking execution when evidence of completion is missing to ensure safe ticket workflow sequencing.

How do I validate my code before submitting a Graphite PR?

Repo validation enforces local correctness by running specified lint, typecheck, and format commands per repository alongside targeted tests, ensuring all required checks pass before submitting a Graphite pull request.

What is dependency gating in a Linear ticket workflow?

Yes, the workflow loads repo authoring guidance from AGENTS.md, CLAUDE.md, and BUGBOT docs, constraining code changes strictly to the ticketed scope unless correctness requires expansion.

Do I need AGENTS.md or CLAUDE.md files to use this ticket workflow?

After running local validations, you create the PR with gt create, submit it with gt submit, and link back to the Linear issue with a factual summary of the implemented changes.

How do I link a Graphite pull request back to a Linear issue?

The workflow constrains changes to ticketed scope by loading repo authoring guidance and limiting modifications to the ticketed scope unless correctness explicitly requires expanding the changes.

What happens if my Linear ticket has unimplemented prerequisite PRs?

The workflow blocks execution when prerequisite tickets or PRs lack evidence of implementation, preventing unsafe code changes and ensuring proper dependency gating before starting new work.