mcpField
L
linear-sync

linear-sync

github.com/tjcagesProductivity1038 installsUpdated 13w ago
Repository

About linear-sync

linear-sync is a Skill for auditing and cleaning up Linear projects, aimed at teams that need structured project reviews and controlled changes. It follows an inspect, score, confirm, fix, and rescore sequence, and requires a search before creating items.

Key features

  1. 01Find and confirm the target project
  2. 02Enumerate issues, milestones, and documents
  3. 03Assess project health with a scoring rubric
  4. 04Confirm categories before making changes
  5. 05Rescore and record status after cleanup

Use cases

  1. 01Review missing issues and milestones in a Linear project
  2. 02Find roadmap documents not mirrored in project tracking
  3. 03Organize dependencies and tracking after confirmation
  4. 04Compare project scores before and after cleanup

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/tjcages/linear --skill linear-sync

After installing, type/linear-syncin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

ALWAYS_ON.md
AUTH.md
AUTOMATION.md
EXAMPLES.md
METHODOLOGY.md
RESPONSE.md

Details

From the project README

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

  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.

Comments

Markdown supported