linear-discipline
Always-on Linear session discipline and one-time soft nudge for untracked repos. Use whenever non-trivial work is happening in a…
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
$ npx -y skills add tjcages/linear --skill linear-monitor --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/linear-monitorContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: linear-monitor version: 1.0.2 description: >- 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 creates. NOT for bootstrap (linear-setup) or full rescue (linear-sync).
Chat rules: [RESPONSE.md](./RESPONSE.md). Auth: [AUTH.md](./AUTH.md). Cadence: [METHODOLOGY.md](./METHODOLOGY.md) §6, §9, §20. Automation recipe: [AUTOMATION.md](./AUTOMATION.md).
Probe Linear MCP. On failure → AUTH.md; **stop**.
User-named team/project, or all accessible teams if unset. **Never** soft-nudge git repos from Automation runs.
1. **Dates** — milestones/issues with targets approaching where work is not trending Done → candidates for `atRisk` (post only if health actually changes). 2. **Stale In Progress** — no comment >7 days → list with links. 3. **Orphans** — issues with no milestone → list. 4. **Anti-patterns glance** — milestone spam, status theater (§19); note only, don’t rewrite unasked.
1. Findings first (≤5 bullets; overflow → later). 2. What you changed (if anything), with links. 3. ONE next action for the human.
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…
Finish Linear tracking pack install after skills are present: write always-on rules (Linear = default source of truth every…
Proven methodology for building and tracking features, projects, and issues in Linear. Use when the user wants to set up Linear…
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…