tracker-sync — Claude Code command: what it does, how to install
tracker-sync projects a flow spec into Linear, GitHub, GitLab, or Jira, then reconciles issue body, status, and comments in both directions.
MIT ★ 730 updated 2026-10-29
/plugin marketplace add gmickel/flow-next
/plugin install flow-next@flow-nextWhat tracker-sync does
tracker-sync connects a flow specification to an issue in an external tracker. It can discover a tracker, create or link a task, push spec changes, pull tracker changes, reconcile both sides, and unlink the connection. The supported trackers are Linear, GitHub, GitLab, and Jira.
The command passes discover, push, pull, reconcile, link, or unlink arguments to the flow-next-tracker-sync skill. It is a projection bridge, not a planning coordinator. /flow-next:sync serves a different job: updating downstream task specs after implementation drift. Because model invocation is disabled, run this command explicitly.
What it helps with
- link a flow spec to an external tracker issue
- push spec body and status to Linear, GitHub, GitLab, or Jira
- pull tracker changes back into the spec
- reconcile issue comments in both directions
- remove an existing spec-to-issue link
Example prompts for the agent
- Run
/flow-next:tracker-sync discoverto find the tracker connection for this flow spec. - Use
/flow-next:tracker-sync link <id>to attach the spec to a tracker issue. - Run
/flow-next:tracker-sync reconcile <id>to compare the body, status, and comments both ways.
How to install tracker-sync
1Plugin marketplace
/plugin marketplace add gmickel/flow-next/plugin install flow-next@flow-next2Manually: put the files in place
.claude/commands/tracker-sync.mdCall it with /tracker-sync. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/tracker-sync.mdCall it with /prompts:tracker-sync. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/tracker-sync.prompt.mdManually: put the files in place
.gemini/commands/tracker-sync.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about tracker-sync
How do I install tracker-sync in Claude Code?
Add the marketplace with /plugin marketplace add gmickel/flow-next, install it with /plugin install flow-next@flow-next, then use .claude/commands/tracker-sync.md.
What does tracker-sync do?
It bridges a flow spec with an issue in Linear, GitHub, GitLab, or Jira and reconciles the issue body, status, and comments in both directions.
How is tracker-sync different from /flow-next:sync?
tracker-sync connects a spec to an external tracker issue. /flow-next:sync updates downstream task specs when implementation has drifted from the plan.
Source text
tracker-sync.md · MIT
--- name: tracker-sync description: Project a flow spec to a tracker (Linear/GitHub/GitLab/Jira) and reconcile body/status/comments two-way — projection, not coordination. NOT plan-sync (/flow-next:sync). argument-hint: "[discover|push|pull|reconcile|link|unlink] [<id>]" disable-model-invocation: true --- # IMPORTANT: This command MUST invoke the skill `flow-next-tracker-sync` The ONLY purpose of this command is to call the `flow-next-tracker-sync` skill. You MUST use that skill now. This is **distinct from `/flow-next:sync`** (= plan-sync, the `flow-next-sync` skill, which updates downstream task specs after implementation drift). `/flow-next:tracker-sync` bridges a spec to an external tracker issue. Do not conflate them. **Arguments:** $ARGUMENTS Pass the arguments to the skill. The skill handles the discovery ceremony, link/create/unlink ceremony, and the push/pull/reconcile orchestration.
© Gordon Mickel · MIT · gmickel/flow-next