Linear sync
Sync, audit, or rescue an existing Linear project against repo reality. Use when the user asks to sync Linear, reconcile tracking, audit this project, fix a messy board, revive a parked project, or score readiness with the rubric. Runs discovery + confirmation before writes; never silent reorganize. NOT for first-time bootstrap (use linear-setup) or one-off CRUD.From its SKILL.md
npx -y skills add tjcages/linear --skill linear-syncAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.7 KB, as published. Nobody here has run it
Linear sync
Chat rules: RESPONSE.md. Auth: AUTH.md. Playbooks: METHODOLOGY.md §1a, §18, §21–§22, §26. Examples: EXAMPLES.md.
Step 0 — auth
Probe Linear MCP. On failure → AUTH.md; stop.
Operating order
- Identify project — search by name; confirm with user if multiple.
- Enumerate — open+closed issues, milestones, labels, documents, status updates (§1a).
- Score — §18 rubric (0–2 × 10). Pass ≥16/20 with no load-bearing 0. Emit gap list.
- Confirm — per-category yes/no before writes. Reorganize is higher-risk than extend.
- Fix in order (§22a): orphans → milestones → milestones spam collapse → dependencies → install/update discipline protocol (§5).
- Half-tracked? — scan
docs/for unmirrored roadmaps (§22b); separate milestone sets. - Backfill-late? — §22c; corroborate doc claims (§4.8).
- One status update recording the cleanup if health/structure changed (§20).
- Re-score — show before/after totals. One next action.
Hard rules
- Search before every create.
- Never delete/reorganize off-limits or other-owned issues without explicit consent.
- Ticket prose stays terse (§4). Chat follows RESPONSE.md.