What problem does it solve? Coordinating Linear issue tracking with GitHub pull requests is error-prone: issues get forgotten in "In Progress", completion context never reaches non-engineer stakeholders, and sub-issue trees lose their ordering. This Skill standardizes the full Linear workflow so issues, comments, and PRs stay synchronized. ## Core Features & Use Cases - Issue Lifecycle Management: Retrieve issues with images, mark In Progress, update status to In Review, and post structured completion comments. - Sub-issue Tree Creation: Build ordered, nested sub-issue hierarchies using title index prefixes and blockedBy dependency ordering to work around Linear MCP limitations. - PR Association: Link PRs to issues with magic keywords like "Fixes LOBE-123" for auto-linking and auto-closing on merge. - Use Case: When implementing a feature tracked as LOBE-456, retrieve the issue with its screenshots, break it into an ordered sub-issue tree, then close out each issue with a status update and completion comment as its PR ships. ## Quick Start Ask the agent to pick up Linear issue LOBE-123, mark it In Progress, implement the fix, and close it out with a PR and completion comment.