linear-discipline
Always-on Linear session discipline and one-time soft nudge for untracked repos. Use whenever non-trivial work is happening in a…
Finish Linear tracking pack install after skills are present: write always-on rules (Linear = default source of truth every session) and verify Linear MCP auth. Optionally offer Cursor Monitor Automation. Use when the user says "finish linear install", "finish linear-tracking
$ npx -y skills add tjcages/linear --skill linear-finish-install --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/linear-finish-installContext preview
The summary Claude sees to decide when to auto-load this skill.
Finish Linear tracking pack install after skills are present: write always-on rules (Linear = default source of truth every session) and verify Linear MCP auth. Optionally offer Cursor Monitor Automation. Use when the user says "finish linear install", "finish linear-tracking
name: linear-finish-install version: 1.0.2 description: >- Finish Linear tracking pack install after skills are present: write always-on rules (Linear = default source of truth every session) and verify Linear MCP auth. Optionally offer Cursor Monitor Automation. Use when the user says "finish linear install", "finish linear-tracking install", "complete setup after skills add", or right after installing the pack.
Chat: [RESPONSE.md](./RESPONSE.md). Auth: [AUTH.md](./AUTH.md). Snippet: [ALWAYS_ON.md](./ALWAYS_ON.md). Optional weekly health: [AUTOMATION.md](./AUTOMATION.md).
**Install is complete** when always-on is loaded and Linear MCP auth works. Same skills + same SoT assumption on every harness. Cursor Automation is optional.
Do these in order. Lead with the next action each turn.
**Cursor:** list user rules. If no rule titled `linear-tracking (always-on)`, add one with `cursor_dialog` (`item=rule`, `scope=user`, `action=add`, title + ALWAYS_ON.md body). If it exists, skip.
**Claude Code / Codex / file-based:** ensure `~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md`, and/or `~/.agents/AGENTS.md` contain the ALWAYS_ON block between markers:
<!-- linear-tracking-always-on --> …ALWAYS_ON.md body… <!-- /linear-tracking-always-on -->
Idempotent: replace the block if markers exist; else append.
Call `list_teams` (or `get_user`).
Useful links:
If this is Cursor and the user wants a weekly digest: open Automations (`open_automation`) and point at [AUTOMATION.md](./AUTOMATION.md). Default schedule Monday **7:00 AM local** (convert cron to UTC — see AUTOMATION.md).
Non-Cursor: skip. They can run `/linear-monitor` anytime.
Do **not** block “install complete” on Automation.
Restate:
1. Always-on: done / already present / failed (where) 2. Linear auth: ok / needs OAuth 3. Install: **complete** if 1+2 ok — Automation offered / skipped / deferred
One next action only.
A proven methodology for building and tracking features, projects, and issues across numerous builds.
Always-on Linear session discipline and one-time soft nudge for untracked repos. Use whenever non-trivial work is happening in a…
Proven methodology for building and tracking features, projects, and issues in Linear. Use when the user wants to set up Linear…
Health-check Linear projects for slipping dates, stale In Progress, and orphan issues. Use when the user asks for a Linear health…
Bootstrap or extend Linear project tracking the right way — methodology, not API CRUD. Use when the user asks to set up Linear…
Sync, audit, or rescue an existing Linear project against repo reality. Use when the user asks to sync Linear, reconcile…