cowork-issue-sync

Create Linear main records with mirrored GitHub issues and bidirectional links.

5|1|Updated May 9, 2026
One-click install
npx skills add https://github.com/ql-link/LinkRag --skill cowork-issue-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cowork-issue-sync
Source: https://github.com/ql-link/LinkRag/tree/main/.ai/skills/cowork-issue-sync
Command: npx skills add https://github.com/ql-link/LinkRag --skill cowork-issue-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

当团队在 Linear 和 GitHub 之间需要将需求、缺陷和新功能转化为结构化的单据时,本 Skill 提供自动化的主记录/镜像工作流,确保两端可追溯且互相定位。

Core Features & Use Cases

  • 自动识别所属项目并在 Linear 创建主记录
  • 在 GitHub 创建镜像 Issue,并将 Linear 的链接写入其中
  • 双向回链:在 Linear 的链接区域记录 GitHub 入口,并在 GitHub 正文末尾附上 Linear 链接
  • 支持多场景:提 issue、登记 bug、记录新需求、跨平台同步

Quick Start

Provide a project issue request and the skill will create a Linear main record, mirror it to GitHub, and establish bidirectional links.

Frequently Asked Questions about cowork-issue-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync issues between Linear and GitHub?

To sync issues between Linear and GitHub, you provide a project issue request and the system automatically creates a Linear main record, mirrors it to GitHub, and establishes bidirectional links for traceability.

Can I automatically create a GitHub issue from a Linear bug report?

Yes, you can automatically create a GitHub issue from a Linear bug report. The workflow mirrors the Linear main record to GitHub and writes the Linear link into the GitHub issue body.

How does bidirectional linking work for Linear and GitHub issues?

Bidirectional linking works by recording the GitHub issue URL in the Linear link area and appending the Linear issue URL to the GitHub issue body, ensuring both platforms can trace and locate each other.

Does this issue sync workflow enforce project mapping and issue templates?

Yes, the issue sync workflow enforces project mapping, issue templates, and linking rules to ensure proper ownership, type classification, and traceability across Linear and GitHub.

What is the best way to track feature requests across Linear and GitHub?

The best way to track feature requests across Linear and GitHub is using an automated cross-platform issue sync workflow that creates a structured main record in Linear and a mirrored issue in GitHub with bidirectional references.

Why do I need a primary record in Linear instead of just creating issues in GitHub?

You need a primary record in Linear to enforce project mapping, issue templates, and ownership rules, while using the mirrored GitHub issue to facilitate developer access and bidirectional traceability.