# sync-conflict-resolver

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.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 1357 repo stars
- Author: qdhenry
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/sync/sync-conflict-resolver.md
- Updated: 2026-03-01
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/qdhenry-sync-conflict-resolver

## What it 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.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/sync-conflict-resolver.md` — Call it with /sync-conflict-resolver. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/sync-conflict-resolver.md` — Call it with /prompts:sync-conflict-resolver. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/sync-conflict-resolver.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/sync-conflict-resolver.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/sync/sync-conflict-resolver.md

## When to use it
- 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
- 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`

## Similar
- [bidirectional-sync](https://affpapa.org/en/nevibecode/commands/bidirectional-sync.md) — command · 133 installs
- [sync-pr-to-task](https://affpapa.org/en/nevibecode/commands/sync-pr-to-task.md) — command · 122 installs
- [sync-automation-setup](https://affpapa.org/en/nevibecode/commands/buildwithclaude-community-sync-automation-setup.md) — command · ★ 3785 repo stars
- [gh-issue-sync](https://affpapa.org/en/nevibecode/skills/gh-issue-sync.md) — skill · 28500 installs
- [sync](https://affpapa.org/en/nevibecode/skills/iurykrieger-sync.md) — skill · ★ 111 repo stars
- [tracker-sync](https://affpapa.org/en/nevibecode/commands/tracker-sync.md) — command · ★ 730 repo stars

## Other versions with the same name
- [sync-conflict-resolver · davila7](https://affpapa.org/en/nevibecode/commands/sync-conflict-resolver.md) — 135 installs

From the same set: [qdhenry/claude-command-suite](https://affpapa.org/en/nevibecode/by/qdhenry/claude-command-suite.md) — 112 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
