Skip to content
Skills Library
Management & product · Review & audit

linear-sync

/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.

Repository
linear ↗
Licence
MIT
Last repository change
29.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
7
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author description

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.

How it works

  1. Step 0 — auth
  2. Operating order
  3. Hard rules
Original SKILL.md headings · 27 lines, 170 words
SKILL.md preview
---
name: linear-sync
version: 1.0.2
description: >-
  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.
---

# Linear sync

Chat rules: [RESPONSE.md](./RESPONSE.md). Auth: [AUTH.md](./AUTH.md). Playbooks: [METHODOLOGY.md](./METHODOLOGY.md) §1a, §18, §21–§22, §26. Examples: [EXAMPLES.md](./EXAMPLES.md).

## Step 0 — auth

Probe Linear MCP. On failure → AUTH.md; **stop**.

## Operating order

1. **Identify project** — search by name; confirm with user if multiple.
2. **Enumerate** — open+closed issues, milestones, labels, documents, status updates (§1a).
3. **Score** — §18 rubric (0–2 × 10). Pass ≥16/20 with no load-bearing 0. Emit gap list.
4. **Confirm** — per-category yes/no before writes. Reorganize is higher-risk than extend.
5. **Fix in order** (§22a): orphans → milestones → milestones spam collapse → dependencies → install/update discipline protocol (§5).
6. **Half-tracked?** — scan `docs/` for unmirrored roadmaps (§22b); separate milestone sets.
7. **Backfill-late?** — §22c; corroborate doc claims (§4.8).
8. **One status update** recording the cleanup if health/structure changed (§20).
9. **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.
Files in this package (7)
  • ALWAYS_ON.md 1 KB
  • AUTH.md 1 KB
  • AUTOMATION.md 3 KB
  • EXAMPLES.md 5 KB
  • METHODOLOGY.md 55 KB
  • RESPONSE.md 2 KB
  • SKILL.md 2 KB

Versions

RepositoryScoreLicence
This page · tjcages/linear100MIT
ray-aqno/toto-wolff98MIT

Database snapshot: 13.11.2026 · package version 4e4941c22a6b (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

  • 95linear-issue-sync
    Sync Linear issues with local tasks. Use during daily planning or when user asks about Linear issues.
  • 90sync-project
    Reconcile a workspace project's config with its backend (Linear/hub) project. Use when the user invokes /dev-loop:sync-project, or asks to "sync the project", "reconcile with Linear", "the project was renamed/archived in Linear", or "check config vs backend drift". Read-only by…
  • 90linear-monitor
    Health-check Linear projects for slipping dates, stale In Progress, and orphan issues. Use when the user asks for a Linear health check, atRisk scan, monitoring, /linear-monitor, or when a Cursor Automation runs the Linear tracking health recipe. Default read + comment; no mass…
  • 85linear-setup
    Bootstrap or extend Linear project tracking the right way — methodology, not API CRUD. Use when the user asks to set up Linear tracking, track this project in Linear, add this repo to Linear, backfill history, get ready to track, or consents after a soft-nudge from…
  • 96linear-project-management
    Use this skill when driving Linear projects and issues from an agent.
  • 100linear-issue-sync
    Sync Linear issues with local tasks. Use during daily planning or when user asks about Linear issues.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.