Engineering
linear avatar

linear

Linear issue management and synchronization for LobeHub, featuring automated PR referencing, sub-issue tree decomposition, and status tracking.

Introduction

The Linear skill provides a comprehensive bridge between the LobeHub agent environment and Linear issue management. It is designed for engineering teams that need to maintain synchronization between their coding workflow and project tracking. By leveraging the LobeHub agent's capability to read issues, update statuses, and create structured task hierarchies, developers can ensure that project management reflects real-time progress without manual context switching. The skill is triggered automatically when referencing LOBE-xxx issue identifiers or performing PR operations.

  • Full lifecycle management of Linear issues including retrieval, status updates (In Progress, In Review, Done), and comment synchronization.

  • Advanced sub-issue tree construction, enabling automated creation of complex task dependencies, nested project structures, and ordering indices for readability.

  • PR-Linear binding features that enforce the inclusion of magic keywords (Fixes, Closes, Resolves) to maintain traceability between code commits and tasks.

  • Visual and contextual data processing, including the ability to extract and interpret images from issue descriptions for better task understanding.

  • Required completion commentary workflows, ensuring that every task closure includes a detailed summary of changes, files modified, and associated PR links for better team visibility.

  • Always search for the 'linear' MCP tool first to confirm integration availability.

  • Use the mcp__linear-server__extract_images tool if issue details contain relevant visual context.

  • When breaking down tasks, use top-down numbering (e.g., [1], [1.1]) to visualize dependencies and maintain logical flow in the sub-issue panel.

  • Always add the 'claude code' label when creating new issues to facilitate easier filtering.

  • Adhere to the mandatory completion comment format to provide sufficient context for reviewers and future code maintainers.

  • Remember that status updates to 'In Review' must occur exactly when a PR is opened, while 'Done' is reserved for post-merge actions.

Repository Stats

Stars
75,884
Forks
15,041
Open Issues
747
Language
TypeScript
Default Branch
main
Sync Status
Idle
Last Synced
Apr 30, 2026, 12:17 PM
View on GitHub