Skip to main content
command CX Codex

sync-conflict-resolver · qdhenry — Claude Code command: setup and features

The sync-conflict-resolver command for Claude Code identifies and resolves data conflicts between GitHub issues and Linear tasks, merging non-conflicting fields or applying a chosen strategy.

no license ★ 1,357 updated 2026-03-01

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/sync-conflict-resolver.md
Open on GitHub

What sync-conflict-resolver does

This command handles inconsistencies between GitHub items and Linear records. It scans fields such as issue titles, assignees, priorities, and descriptions, surfacing race conditions or deleted entities. Users can apply strategies like latest-wins, trigger step-by-step interactive resolution, or preview modifications via --dry-run.

The routine supports field merging for non-conflicting sections and creates backups prior to committing changes. Execution fails unless GitHub CLI is configured alongside active mcp-server-github and mcp-server-linear instances.

What it helps with

  • detect mismatched fields between GitHub tickets and Linear items
  • resolve issue discrepancies automatically with the latest-wins policy
  • merge non-conflicting description changes without manual copy-pasting
  • generate conflict analytics and frequency trends for recent sync runs

Example prompts for the agent

  • Scan all tracked issues for collisions: sync-conflict-resolver detect
  • Resolve differences interactively with a safety backup: sync-conflict-resolver resolve --interactive --backup
  • Preview automated resolution without making changes: sync-conflict-resolver resolve --auto-resolve --dry-run

How to install sync-conflict-resolver

Manually: put the files in place

.claude/commands/sync-conflict-resolver.md

Call it with /sync-conflict-resolver. For all projects use ~/.claude/commands/

Questions about sync-conflict-resolver

How to install sync-conflict-resolver in Claude Code?

Place the command definition file at .claude/commands/sync-conflict-resolver.md inside your repository.

What does sync-conflict-resolver do?

It compares records across GitHub and Linear, highlights diverging fields, and applies resolution rules to keep both systems aligned.

What prerequisites are needed to run this command?

You need GitHub CLI available in your environment along with running mcp-server-github and mcp-server-linear MCP servers.

Similar slash commands

All slash commands for Notes, tasks and projects →

sync-conflict-resolver by other authors comes first.

sync-conflict-resolver davila7 sync-conflict-resolver resolves data synchronization discrepancies in files like .sync-state.json. Useful for automated field-level merging and conflict error log reviews. CX Codex +1 135installs bidirectional-sync davila7 bidirectional-sync sets up two-way synchronization between GitHub Issues and Linear tasks. Handles update conflicts and tracks state in local JSON files. CX Codex +1 133installs sync-pr-to-task davila7 sync-pr-to-task connects GitHub pull requests with Linear tasks and syncs task state. Use it to keep PR details and task updates together. CX Codex +1 122installs sync-automation-setup BuildWithClaude Community sync-automation-setup configures automated two-way synchronization between GitHub and Linear. Sets up webhooks, background queues, and GitHub Actions workflows. CX Codex +1 ★ 3,785repo stars gh-issue-sync mitsuhiko gh-issue-sync — a skill for Claude Code, Codex, Cursor and other platforms that maps GitHub Issues to local Markdown files. The agent pulls, edits and pushes issues from inside the repo without touching the browser. CX Codex +1 28,500installs sync iurykrieger sync is a Claude Code skill that re-reads vault entity sources, compares them with stored content and passes changes on for writing when notes have drifted from Confluence, GDocs or GitHub. CX Codex +1 ★ 111repo stars tracker-sync Gordon Mickel tracker-sync projects a flow spec into Linear, GitHub, GitLab, or Jira, then reconciles issue body, status, and comments in both directions. CX Codex +1 ★ 730repo stars

From the same set112

The whole set →
performance-auditor performance-auditor — a subagent that hunts bottlenecks: algorithm cost, N+1 queries, bundle size, wasted re-renders. You get a prioritized report. CX Codex ★ 1,357repo stars sync-linear-to-issues sync-linear-to-issues exports Linear tasks into GitHub issues while preserving issue descriptions, sprint milestones, and status mappings. CX Codex +1 ★ 1,357repo stars task-from-pr task-from-pr is a Claude Code command that transfers GitHub pull request details to a Linear task, linking PR work with project tasks. CX Codex +1 ★ 1,357repo stars memory-merge The memory-merge command consolidates multiple semantic tree nodes into one, removing duplicates and grouping related concepts under a single node. CX Codex +1 ★ 1,357repo stars standup-report standup-report builds daily standup updates from Git, GitHub, and Linear, with output suited to a team summary, Slack, or email. CX Codex +1 ★ 1,357repo stars memory-compress memory-compress shrinks the semantic memory tree by merging near-identical nodes and dropping duplicates, while key checkpoints stay put. CX Codex +1 ★ 1,357repo stars memory-prune memory-prune cleans low-value, broken, and outdated nodes from your semantic memory tree. Keeps project context lean and responsive. CX Codex +1 ★ 1,357repo stars elevenlabs-transcribe elevenlabs-transcribe is a Claude Code skill that sends audio and video files to ElevenLabs Scribe v2 and returns a transcript. Set the language, output file, or speaker count. CX Codex +1 ★ 1,357repo stars

Project sponsors

Companies that keep this analytics open