linear-sync
Installation
SKILL.md
linear-sync
Move the Linear issues linked to the current branch through their workflow states. This skill is the single source of truth for how issues are transitioned: extracting the issue ID from a branch name, resolving the live state IDs for each issue's team, and the per-state transition rules. Callers decide when and whether to fire it; the mechanics live here once so the rules don't drift across the ship flow, branch cleanup, and the start-of-work transition.
Configuration
Two knobs live in config.json beside this file. Read it at the
start of a run and use its values throughout. Edit your copied config.json to
match the consuming repo:
| Key | Meaning | Default |
|---|---|---|
linearTeamName |
Fallback Linear team name, used only when an issue's get_issue result carries no team. States are otherwise resolved against each issue's own team. Use the name, not the key — the key is renamed over time but the name is stable. |
"Rheged Studio" |
issueKeys |
Team-key prefixes that may lead a branch name — every team whose issues this repo carries, (e.g. ["R"]). The branch issue-ID regex is built from these. |
["R"] |