skills.rest
paulchiu
paulchiuCOMMUNITY
Explore all skills by this author →
GitHub

linear-do

Automate Linear issue handling from ticket intake through CI monitoring.

3|1|Updated Jun 20, 2016
Search Tags:#automation#git#linear#end-to-end#issue#ci#pull-request
One-click install
npx skills add https://github.com/paulchiu/dotfiles --skill linear-do
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: linear-do
Source: https://github.com/paulchiu/dotfiles/tree/main/.config/opencode/skills/linear-do
Command: npx skills add https://github.com/paulchiu/dotfiles --skill linear-do

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end Linear issue handling from ticket ingestion through CI monitoring, reducing manual handoffs and delays.

Core Features & Use Cases

  • End-to-end Linear issue workflow: read ticket, implement changes, commit, open a PR, and monitor CI.
  • Automatic branch naming based on Linear issue identifiers and conventional git practices.
  • Phase-driven collaboration: prompts for clarifications before starting work and guides safe, scoped changes.

Quick Start

Provide a Linear issue URL or ID to begin processing an end-to-end update.

Frequently Asked Questions about linear-do

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

FAQPage Schema
How do I automate Linear issue handling from ticket intake to CI verification?▼

Automate Linear issue handling by providing a ticket URL or ID to trigger end-to-end processing, which reads the ticket, orchestrates git workflows, drafts a pull request, and monitors CI status checks automatically.

Can I automatically generate git branch names from Linear issue identifiers?▼

Yes, branch naming is automated based on Linear issue identifiers and conventional git practices. The Skill reads the ticket metadata and applies standardized naming conventions to ensure consistent branch creation.

How does end-to-end Linear issue automation handle pull request creation?▼

Pull request creation is handled by orchestrating the git workflow after implementing changes. The Skill drafts the PR automatically once code modifications are committed, linking the work directly back to the original Linear issue.

Do I need to integrate Linear APIs or a CLI to automate ticket workflow orchestration?▼

Yes, integrating with Linear APIs or CLI is required to automate the ticket workflow. This integration enables the Skill to read ticket details, apply branch naming, and monitor CI verification status effectively.

What is the best way to ensure scoped changes when automating software engineering tasks for Linear tickets?▼

The best way to ensure scoped changes is through phase-driven collaboration. The Skill prompts for clarifications before starting work, guiding safe and focused modifications directly tied to the specific Linear issue requirements.

Why does the automation prompt for clarifications before starting work on a Linear issue?▼

The automation prompts for clarifications to enforce phase-driven collaboration and ensure safe, scoped changes. This step verifies ticket requirements before implementation, reducing manual handoffs and preventing out-of-scope modifications.

Related Skills

Explore More Software Engineering Skills→
bradtaylorsfbradtaylorsf
8

ticket-status-sync

Synchronizes Linear ticket statuses with Git workflow events via API and gh CLI.

Community
Advanced
adryanmoldokkr32-pixeladryanmoldokkr32-pixel

land-and-deploy

Merge pull requests, monitor CI, deploy to production, and verify health with canary checks.

Community
Intermediate
chtughachtugha

review-readiness

Monitor pull request readiness across code review, tests, security, QA, and linting.

Community
Intermediate
gabrielfruetgabrielfruet
3

linear-cli

Manage Linear issues, projects, and teams from the command line.

Community
Intermediate