linear-github-sync

Synchronize Linear issues with GitHub branches, commits, and pull requests.

Updated Dec 4, 2025
One-click install
npx skills add https://github.com/dallascrilley/dowser --skill linear-github-sync-dallascrilley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: linear-github-sync
Source: https://github.com/dallascrilley/dowser/tree/main/skills/linear-github-sync
Command: npx skills add https://github.com/dallascrilley/dowser --skill linear-github-sync-dallascrilley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires linctl, git, gh, jq, curl, and includes scripts (resource) and references (resource) components.

What problem does it solve? Teams tracking work in Linear while coding on GitHub often lose traceability between issues and code changes. This Skill enforces naming conventions and workflows that keep Linear issues automatically linked to branches, commits, and PRs. ## Core Features & Use Cases - Project Setup Automation: Detects the GitHub repository and creates a matching Linear project, updating README.md, CLAUDE.md, and AGENTS.md with the project reference. - Branch and Commit Conventions: Creates branches named <type>/<issue-id>-<slug> and formats commit messages with issue IDs so Linear auto-links all GitHub activity. - PR Linking and Auto-Close: Uses Fixes DAL-123 or Closes DAL-123 in PR descriptions to automatically close Linear issues on merge. - Use Case: A developer picks up issue DAL-123, runs the branch creation script, commits with the issue ID, opens a PR with "Fixes DAL-123", and the Linear issue closes automatically when the PR merges. ## Quick Start Ask the assistant to start work on Linear issue DAL-123 by creating a properly named branch and updating the issue status to In Progress.

Frequently Asked Questions about linear-github-sync

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

FAQPage Schema
How do I link a GitHub branch to a Linear issue?▼

Name the branch with the Linear issue ID using the format `<type>/<issue-id>-<slug>`, such as `feature/dal-123-add-authentication`. Linear automatically detects and links branches containing issue IDs, and the included script creates properly named branches for you.

How do I auto-close a Linear issue when a PR merges?▼

Include `Fixes DAL-123` or `Closes DAL-123` in the PR description. When the PR merges, Linear automatically updates the issue status to Done. Use `Related to DAL-123` to link without auto-closing.

What tools are required for Linear GitHub synchronization?▼

You need the linctl CLI installed and authenticated with a Linear API key, plus git and jq. The GitHub CLI (gh) is optional but useful for creating PRs and detecting repository names.

Why didn't my Linear issue close after merging the PR?▼

The PR description must contain `Fixes DAL-XXX` or `Closes DAL-XXX` for auto-closing to trigger. If it was missed, manually close the issue with `linctl issue update DAL-123 --state "Done" --json`.

Can linctl set blocking relationships between Linear issues?▼

No, linctl does not support blocking relationships directly. The included set-linear-blockers.sh script calls the Linear GraphQL API with your API key to create issueRelation entries of type blocks.