skills.rest
bradtaylorsf
bradtaylorsfCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ticket-status-sync

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

8|2|Updated Jan 15, 2026
Search Tags:#automation#git#workflow#ticket management#linear#sync
One-click install
npx skills add https://github.com/bradtaylorsf/alphaagent-team --skill ticket-status-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-status-sync
Source: https://github.com/bradtaylorsf/alphaagent-team/tree/main/plugins/aai-pm-linear/skills/ticket-status-sync
Command: npx skills add https://github.com/bradtaylorsf/alphaagent-team --skill ticket-status-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the tedious process of manually updating Linear ticket statuses based on Git workflow events, ensuring your project management tool accurately reflects development progress.

Core Features & Use Cases

  • Automated Status Updates: Automatically transitions Linear tickets through states like "In Progress", "In Review", and "Done" based on branch creation, PR events, and merges.
  • Contextual Comments: Adds relevant Git information (branch names, PR links) as comments to Linear tickets for better traceability.
  • Use Case: When you create a new branch for a specific ticket (e.g., feature/PROJ-123-add-login), this Skill automatically sets the corresponding Linear ticket to "In Progress" and adds a comment with the branch details.

Quick Start

Use the ticket-status-sync skill to automatically update the Linear ticket status when a new Git branch is created.

Frequently Asked Questions about ticket-status-sync

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

FAQPage Schema
How do I automatically sync Linear ticket statuses with Git workflow events?▼

You can sync Linear ticket statuses with Git events by extracting ticket IDs from branch names and pull requests, then updating ticket states via the Linear API based on branch creation, PR events, and merges.

Do I need the gh CLI to update Linear tickets from pull request events?▼

Yes, you need the gh CLI to retrieve pull request information when synchronizing Linear ticket statuses with Git workflow events such as PR openings and merges.

How does branch creation trigger a Linear ticket status update?▼

When a new Git branch is created, the Skill extracts the ticket ID from the branch name, transitions the corresponding Linear ticket to In Progress, and adds a contextual comment with the branch details.

Can I add pull request links as comments to Linear tickets automatically?▼

Yes, the Skill adds relevant Git information including pull request links and branch names as comments to Linear tickets to improve project traceability during development.

What is the best way to transition Linear tickets to Done when a branch is merged?▼

The best way to transition Linear tickets to Done is by using a synchronization Skill that detects Git merge events and automatically updates the ticket status via the Linear API.

What are the limitations of syncing Linear ticket statuses with Git events?▼

The synchronization requires Linear API access for ticket manipulation and relies on extracting valid ticket IDs from branch names and PRs, meaning branches without proper ticket IDs will not trigger status updates.

Related Skills

Explore More Product & Management Skills→
afel6afel6

github-auth

Configure GitHub authentication for git or gh CLI access.

Community
Intermediate
amplitudeamplitude
142

release-notes-generator

Generate user-facing release notes from Linear, Jira, and GitHub Issues into a .docx file.

Official
Intermediate
AnveioAnveio
1

task-pull-request

Automate GitHub pull request creation, reviews, feedback, and merges via gh CLI.

Community
Intermediate
semicolon-devteamsemicolon-devteam

sync-project-status

Synchronize GitHub Projects statuses with Issue states via GraphQL mutations.

Official
Intermediate