tjcages/linear · Archived

linear-discipline

>- Always-on Linear session discipline and one-time soft nudge for untracked repos. Use whenever non-trivial work is happening in a repo that already has a Linear tracking protocol in CLAUDE.md, AGENTS.md, or .cursor/rules; or when opening/working in a repo with no protocol and no .linear-tracking-skip file (ask once to run linear-setup). Enforces search-before-create, lifecycle, and close-the-loop. NOT for full bootstrap, sync, or monitor runs.

First seen Jul 30, 2026

Installation

$ npx skills add tjcages/linear --skill linear-discipline

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from tjcages/linear.

npx skills add tjcages/linear

Browse all from tjcages/linear

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 9
License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.2
Declared agents claude-code cursor

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,928 B
  • docs SUMMARY.md 471 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 30 installs

SKILL.md

Linear discipline (always-on)

Chat rules: [RESPONSE.md](./RESPONSE.md). Auth before Linear calls: [AUTH.md](./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:

  1. Search before create.
  2. Non-trivial work → file/update an issue in the named project + milestone.
  3. Backlog → In Progress at start → Done only when shipped.
  4. Close the loop before session end (state and/or comment).
  5. 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-skip at repo root; stay quiet next time.
  • Never auto-create Linear projects or issues from a nudge alone.
  • Never nudge from Automation / linear-monitor runs.

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.