sync-linear

Synchronize current branch work with Linear ticket, ensuring ticket reflects actual progress.

Sync Workflow

1. Get Current Ticket

Extract WOR number from branch:

git branch --show-current | grep -oE '{{TICKET_PREFIX}}-[0-9]+'

Fetch ticket details:

mcp__{{MCP_LINEAR_SERVER}}__get_issue {{{TICKET_PREFIX}}-number}

2. Analyze Work Done

Check commits since dev:

git log origin/dev..HEAD --oneline
git diff origin/dev --stat

Analyze:

• Number of commits
• Files changed
• Lines added/removed
• Work scope

3. Determine Status

Based on work analysis:

If commits exist but incomplete:

• Status: "In Progress"
• Add progress comment

If work complete, no PR:

• Status: "Ready for Review" or keep "In Progress"
• Add completion comment

If PR created:

• Status: "In Review"
• Link PR in comment

If PR merged:

• Status: "Done" (often auto-synced by GitHub-Linear integration for tickets referenced in commit messages)
• Manually close any child stories not referenced in commits
• Add completion timestamp

If blocked:

• Status: "Blocked"
• Document blocker

4. Update Ticket Status

Use Linear MCP to update:

mcp__{{MCP_LINEAR_SERVER}}__update_issue

Update fields:

• Status (based on analysis)
• Progress percentage (if tracked)
• Labels (add "in-progress", "blocked", etc.)

5. Add Progress Comment

Create detailed comment:

## Progress Update - {date}

### Work Completed

- {commit 1 summary}
- {commit 2 summary}
- {commit 3 summary}

### Files Modified

- {file list with line counts}

### Next Steps

1. {next task}
2. {next task}

### Blockers

- {blocker if any}

### Timeline

- Started: {date}
- Current: {percentage}% complete
- Est. completion: {date/unknown}

Add comment via:

mcp__{{MCP_LINEAR_SERVER}}__create_comment

6. Link Related Items

If applicable:

• Link to PR (if created)
• Link to related tickets
• Link to documentation
• Reference design docs