Verified:GitHub

tracker-sync

Synchronize issues, labels, and statuses across GitHub, Jira, Linear, and GitLab.

Updated Apr 17, 2026

Search Tags:#automation #github #linear #jira #gitlab #tracker-sync

One-click install

npx skills add https://github.com/ctxr-dev/agent-staff-engineer --skill tracker-sync

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: tracker-sync
Source: https://github.com/ctxr-dev/agent-staff-engineer/tree/main/skills/tracker-sync
Command: npx skills add https://github.com/ctxr-dev/agent-staff-engineer --skill tracker-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Centralizes tracker API calls and guarantees idempotent read/write across major trackers (GitHub, Jira, Linear, GitLab), helping teams keep issues, labels, and project data consistent.

Core Features & Use Cases

Centralized dispatcher that routes all tracker operations through a single policy (depth checks, authorization handling, and safe retries).
Supports issues, labels, statuses, and comments across GitHub, Jira, Linear, and GitLab, with per-kind nuances and backends implemented or stubbed.
Enables cross-tracker workflows like issue creation, status updates, labeling, and release planning, while preserving per-target guardrails and audit trails.

Quick Start

Configure ops.config.json with your trackers and run the bootstrap or agent startup to begin syncing tracker state.

Frequently Asked Questions about tracker-sync

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

FAQPage Schema

How do I sync issue statuses across GitHub, Jira, Linear, and GitLab?▼

To sync issue statuses across GitHub, Jira, Linear, and GitLab, this Skill uses a centralized dispatcher to route idempotent read and write operations to each tracker API, ensuring consistent issue data, statuses, and labels across all platforms.

What is the best way to automate cross-tracker issue updates and labeling?▼

Automating cross-tracker issue updates and labeling is best handled through a unified sync policy that applies per-target depth controls and authorization checks, safely creating issues, updating statuses, and applying labels across configured trackers.

Can I test tracker sync operations before applying changes to my repositories?▼

Yes, you can test tracker sync operations before applying changes by using the supported dry-run mode, which evaluates dispatcher operations against your tracker APIs without committing the actual status or label updates.

How do I configure cross-tracker workflows for release planning?▼

You can configure cross-tracker workflows for release planning by defining your target connections in ops.config.json, then running the bootstrap to start syncing project data, issues, and statuses across your specified trackers.

What happens if an unsupported backend is used during issue synchronization?▼

If an unsupported backend is used during issue synchronization, the dispatcher enforces a NotSupportedError to halt the operation, preventing invalid API calls and preserving per-target guardrails and audit trails for safe rollback.

Does tracker-sync work with GitLab and Jira for commenting and status updates?▼

Yes, tracker-sync works with GitLab and Jira for commenting and status updates, supporting issues, labels, statuses, and comments across GitHub, Jira, Linear, and GitLab with per-kind nuances and backends implemented or stubbed.