bidirectional-sync · qdhenry — Claude Code command: sync GitHub and Linear
bidirectional-sync — a slash command that pairs GitHub issues with Linear tasks and copies edits both ways, settling the ones that landed on both sides.
no license ★ 1,357 updated 2026-03-01
.claude/commands/bidirectional-sync.mdWhat bidirectional-sync does
Point this command at a repo and a Linear team, and Claude starts matching GitHub issues to Linear tasks in both directions. It needs the GitHub CLI and Linear MCP already set up, otherwise there is nothing to talk to. Each pair gets a record with both ids, the last edit time on each side and a hash, so the next run knows what moved.
Edits to the same item are caught by comparing timestamps. The default takes the newer one; GITHUB_WINS, LINEAR_WINS, MANUAL_MERGE and FIELD_LEVEL_MERGE are the alternatives. Under field-level merge, priority follows Linear, labels are unioned, comments are appended. A [sync-bot] marker plus a 30-second pause after each run keeps the two sides from echoing updates back and forth.
Per-label rules live in .github/linear-sync.yml — bug reports can be pushed to priority 1, drafts skipped. Run with --dry-run first to see the change list before anything is written.
What it helps with
- match GitHub issues to Linear tasks and spot the gaps
- settle an item that was edited on both sides
- push bug reports to priority 1 with a label rule
- preview a sync with
--dry-runbefore writing anything - stop sync runs from bouncing updates back and forth
Example prompts for the agent
/bidirectional-syncrun a full sync between GitHub Issues and Linear./bidirectional-syncsettle conflicts with the LINEAR_WINS strategy./bidirectional-syncdo a dry run and show me the change list.
How to install bidirectional-sync
Manually: put the files in place
.claude/commands/bidirectional-sync.mdCall it with /bidirectional-sync. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/bidirectional-sync.mdCall it with /prompts:bidirectional-sync. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/bidirectional-sync.prompt.mdManually: put the files in place
.gemini/commands/bidirectional-sync.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about bidirectional-sync
How do I install bidirectional-sync in Claude Code?
Put the command file at .claude/commands/bidirectional-sync.md.
What does bidirectional-sync do?
It keeps GitHub issues and Linear tasks matched and copies edits both ways, resolving conflicts as it goes.
Which conflict strategy does it use by default?
NEWER_WINS: the most recent edit on either side takes over. You can switch to GITHUB_WINS, LINEAR_WINS, MANUAL_MERGE or FIELD_LEVEL_MERGE.
Similar slash commands
All slash commands for Git and GitHub →bidirectional-sync by other authors comes first.