ticket-status-sync
Synchronizes Linear ticket status with git workflow events.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Synchronizes Linear ticket status with git workflow events.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Patterns for generating Gamma.app-compatible slide deck markdown from GitHub data for customer-facing account management presentations
Patterns for generating Gamma.app-compatible slide deck markdown from Linear data for customer-facing account management presentations
Patterns and templates for creating sprint/project retrospective reports from Jira data with time tracking and blocker analysis.
Multi-platform Electron build configuration - esbuild bundling, electron-builder setup, and distribution
Integrate external CLI tools (Claude, Node, npx) in Electron apps with proper PATH handling
Handle native Node.js modules in Electron - better-sqlite3, sharp, keytar packaging patterns
| name | ticket-status-sync |
| description | Synchronizes Linear ticket status with git workflow events. |
| user-invocable | false |
Synchronizes Linear ticket status with git workflow events, keeping tickets up-to-date with development progress.
Automatically update Linear tickets when:
Important: Always ask user permission before updating Linear.
Git Event -> Linear Status
-----------------------------------------
Branch created -> In Progress
PR created -> In Review
PR merged -> Done
PR closed (no merge) -> Todo
PR draft -> In Progress
Branch Creation:
# After creating branch
# Example: feature/PROJ-123-add-oauth-support
PR Creation:
gh pr view [number] --json number,state,isDraft,headRefName
PR Status Change:
gh pr view [number] --json state,merged,mergedAt,closedAt
From branch name:
git branch --show-current
# Pattern: {type}/{ticket-id}-{description}
# Extract: PROJ-123
From PR:
gh pr view [number] --json headRefName
mcp__linear__get_issue --id PROJ-123
If ticket not found:
Warning: Ticket PROJ-123 not found in Linear.
Skip status update? (yes/no)
Format:
Linear Ticket Update
Ticket: PROJ-123 - Add OAuth2 support
Current Status: In Progress
Proposed Status: In Review
Reason: PR #456 created
Update ticket? (yes/no/never)
mcp__linear__update_issue \
--id PROJ-123 \
--state "In Review"
Branch created:
Started work in branch: `feature/PROJ-123-add-oauth-support`
Base: main
PR created:
Pull request created: [#456](PR_URL)
Branch: `feature/PROJ-123-add-oauth-support`
Target: main
PR merged:
Pull request merged: [#456](PR_URL)
Merged to: main
Linear ticket updated
Ticket: PROJ-123
Status: Todo -> In Review
Comment: Added PR link #456
URL: https://linear.app/team/issue/PROJ-123
Linear API error:
Error: Failed to update Linear ticket
Details: {error}
Actions:
[1] Retry
[2] Skip for now
[3] Update manually: {ticket_url}
Invalid state transition:
Error: Cannot transition from "Done" to "In Progress"
Skip update? (yes/no)
This skill is invoked by:
/ticket-start - When creating branch/push - When creating PRUsed by agents:
linear-ticket-planner - Updates status when starting workgit-pr-manager - Updates status when creating PRMultiple PRs for one ticket:
Notice: Multiple PRs found for PROJ-123
PRs:
- #456 (open, in review)
- #789 (merged)
Which PR triggered this update?
Ticket already Done:
Notice: Ticket PROJ-123 is already marked Done
Actions:
[1] Keep ticket as Done
[2] Reopen ticket (-> In Progress)
[3] Create new follow-up ticket
Draft PR:
Notice: PR #456 is in draft mode
Status: In Progress (not In Review)
Mark as In Review when PR is ready:
gh pr ready
Before updating ticket: