Linear issue management. MUST USE when: (1) user mentions LOBE-xxx issue IDs (e.g. LOBE-4540), (2) user says 'linear', 'linear issue', 'link linear', (3) creating PRs that reference Linear issues. Provides workflows for retrieving issues, updating status, and adding comments.
Before using Linear workflows, search for linear MCP tools. If not found, treat as not installed.
When creating a PR that references Linear issues (LOBE-xxx), you MUST:
Fixes LOBE-xxx)This is NON-NEGOTIABLE. Skipping Linear comments is a workflow violation.
mcp__linear-server__get_issuemcp__linear-server__extract_images to read image content for full contextmcp__linear-server__list_issues with parentId filtermcp__linear-server__update_issuemcp__linear-server__update_issuemcp__linear-server__create_commentWhen creating issues with mcp__linear-server__create_issue, MUST add the claude code label.
Every completed issue MUST have a comment summarizing work done:
## Changes Summary
- **Feature**: Brief description of what was implemented
- **Files Changed**: List key files modified
- **PR**: #xxx or PR URL
### Key Changes
- Change 1
- Change 2
- ...
This is critical for:
When creating PRs for Linear issues, include magic keywords in PR body:
Fixes LOBE-123Closes LOBE-123Resolves LOBE-123When working on multiple issues, update EACH issue IMMEDIATELY after completing it:
bun run type-checkNote: Status → "In Review" when PR created. "Done" only after PR merged.
❌ Wrong: Complete all → Create PR → Forget Linear comments
✅ Correct: Complete → Create PR → Add Linear comments → Task done