How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/tjcages/linear --skill linear-disciplineBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Linear discipline (always-on)
Chat rules: RESPONSE.md. Auth before Linear calls: AUTH.md.
Detect tracking
Tracked if the repo has a “Linear tracking” (or equivalent) section in CLAUDE.md, AGENTS.md, or .cursor/rules/* that names team + project.
Skipped if .linear-tracking-skip exists at repo root.
If tracked
Follow the protocol written in-repo:
- Search before create.
- Non-trivial work → file/update an issue in the named project + milestone.
Backlog→In Progressat start →Doneonly when shipped.- Close the loop before session end (state and/or comment).
- Prefer Linear’s generated branch names.
Before any Linear tool call: Step 0 auth.
If untracked and not skipped (soft nudge — 1B)
Ask once, one line, no preamble:
This repo isn’t tracked in Linear. Set it up now? (~10–20 min)
- Yes → hand off to
linear-setup(do not bootstrap inline without that skill’s gates). - No → create
.linear-tracking-skipat repo root; stay quiet next time. - Never auto-create Linear projects or issues from a nudge alone.
- Never nudge from Automation /
linear-monitorruns.
If skipped
Stay quiet about setup. Still use Linear MCP for explicit user requests.
Out of scope
Full bootstrap → linear-setup. Rescue/audit → linear-sync. Health digest → linear-monitor.
