backlog-sync
/backlog-sync
Run or add a one-way sync profile between two Backlog spaces with backlog-bridge sync — mirror mode (create internal mirror issues from planned customer tasks) and progress mode (push internal progress onto the customer's existing issues). Use when the user says "sync the customer tasks", "mirror ACME into DEV", "push progress to the customer", "add a sync for a new customer", "dry-run the sync".
- Author
- mickey-ichi ↗
- Repository
- backlog-bridge ↗
- Licence
- MIT
- Last repository change
- 07.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Run or add a one-way sync profile between two Backlog spaces with backlog-bridge sync — mirror mode (create internal mirror issues from planned customer tasks) and progress mode (push internal progress onto the customer's existing issues). Use when the user says "sync the customer tasks", "mirror ACME into DEV", "push progress to the customer", "add a sync for a new customer", "dry-run the sync".
Triggers from the description
Original author description
Run or add a one-way sync profile between two Backlog spaces with backlog-bridge sync — mirror mode (create internal mirror issues from planned customer tasks) and progress mode (push internal progress onto the customer's existing issues). Use when the user says "sync the customer tasks", "mirror ACME into DEV", "push progress to the customer", "add a sync for a new customer", "dry-run the sync".
How it works
- List profiles
- Run — always preview first
- Common warnings
- Add a profile for a new project pair
SKILL.md preview
--- name: backlog-sync description: Run or add a one-way sync profile between two Backlog spaces with backlog-bridge sync — mirror mode (create internal mirror issues from planned customer tasks) and progress mode (push internal progress onto the customer's existing issues). Use when the user says "sync the customer tasks", "mirror ACME into DEV", "push progress to the customer", "add a sync for a new customer", "dry-run the sync". --- # Sync between two Backlogs The rules of each mode are in `README.md` — read the relevant section before changing a profile. ## List profiles ```bash backlog-bridge sync --list ``` ## Run — always preview first | Mode | Default | Preview | Real write | |---|---|---|---| | `mirror` (destination = internal) | **LIVE** | `--dry-run` | drop `--dry-run` | | `progress` (destination = customer) | **DRY** | (default) | `--live` | ```bash # mirror: filter by member + due date backlog-bridge sync --profile=acme --dry-run --assignee=An --since=2026-10-01 backlog-bridge sync --profile=acme --assignee=An --since=2026-10-01 # progress: review the rollup, then write to the customer backlog-bridge sync --profile=acme-progress backlog-bridge sync --profile=acme-progress --live --comment ``` Flow: run the preview → summarize for the user (how many creates / updates / `!` warnings) → run the real write only after they agree. `progress` writes to the **customer's** Backlog → always ask again. Don't use `--update` (mirror) or `--allow-regress` (progress) unless the user explicitly asks. ## Common warnings - `! No status/priority/issueType match` → add it to `profiles.<name>.map`. - `! "<name>" not found in <PROJECT>` → add `map.assignee` if names differ between the two spaces. - `! Required custom field ... is not set` / `... is required` → declare `dest.customFields` (by field name + item name). - `401` → key expired; `403 Inactive Licence` → the space is inactive. See skill `backlog-connect`. ## Add a profile for a new project pair 1. Connect both spaces (skill `backlog-connect`). Profiles live in the config in the home directory (`backlog-bridge home` shows the path); start from `config.example.json` (its path is printed by `backlog-bridge setup`). 2. Fetch the real status / issue type names on both sides to build `map`: ```bash backlog-bridge api <srcSpace> GET /projects/<SRC>/statuses backlog-bridge api <srcSpace> GET /projects/<SRC>/issueTypes backlog-bridge api <dstSpace> GET /projects/<DST>/statuses backlog-bridge api <dstSpace> GET /projects/<DST>/issueTypes ``` 3. Copy the `acme` (mirror) profile, change `source` / `dest` / `state` (its own state file, relative to the home directory), `map`, `note`. `progress` is more involved — read the README section first. 4. `backlog-bridge sync --profile=<name> --dry-run` and show the result to the user before running for real.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · mickey-ichi/backlog-bridge | 100 | MIT |
| mickey-ichi/backlog-bridge | 100 | MIT |
Database snapshot: 13.11.2026 · package version 5d0fa31a92a8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100backlog-query
Read issues, comments, search results and activity across MANY Backlog spaces via the backlog-bridge CLI. Use when the user pastes a Backlog link or issue key (e.g. https://acme.backlog.jp/view/ACME-123, DEV-42), asks "what's the status of this task", "find tasks assigned to X",… - 100backlog-query
Read issues, comments, search results and activity across MANY Backlog spaces via the backlog-bridge CLI. Use when the user pastes a Backlog link or issue key (e.g. https://acme.backlog.jp/view/ACME-123, DEV-42), asks "what's the status of this task", "find tasks assigned to X",… - 90Backlog Management
This skill should be used when the user asks to 'add to backlog', 'update backlog', 'check backlog', 'list backlog items', 'prioritize backlog'. Provides conventions for managing the project backlog in .s2s/BACKLOG.md. - 90session
Cross-session continuity and backlog/process rules — how project state, outstanding work, and documentation survive between sessions. Covers the session handoff, PROGRESS.json as the single backlog source, the GitHub Issues/Projects mirror, documentation maintenance, and the… - 84backlog
Manage the structured product backlog — pick what to work on next, add/find/list/update items, and migrate legacy items. Use when the user wants to triage, file, or choose backlog work, or says /prawduct:backlog. - 100backlog
Manage this workspace's Markdown tasks through Backlog.md. Use when creating, splitting, selecting, tracking, or closing tasks, or when the user mentions the backlog, task IDs, acceptance criteria, or a Definition of Done.