Attach the current Claude Code session to a Linear issue so plans and PRs uploaded later land on that issue. Uses the link-session verb via linear.mjs. Use when: engineer says "link this session to TEAM-42", "track this work on Linear issue X", pastes a Linear issue URL and asks to pick it up, or /linear-link-session <id>. Skip when: engineer explicitly wants to work WITHOUT a Linear ref — the feature is optional.
File a bug in your Linear team with the required Type/Area/env labels and PII scan. Uses the log-bug verb via linear.mjs. Rejects the create when DOB or government ID is detected. Use when: engineer says "log a bug", "file a bug", "create a bug ticket", "report this bug", or /linear-log-bug. Skip when: engineer wants to discuss the bug first; or intends to work on it without tracking in Linear (Linear ref is optional).
Pick a Todo (Ready) issue from your Linear team to start work on. Uses the pick-task and start-task verbs via linear.mjs to list candidates, then claim one (move to In Progress, assign self, print branch/worktree hint). Use when: engineer says "what's next", "pick a task", "start on a Linear issue", "find me something to do", or /linear-pick-task. Skip when: engineer has a specific task in mind outside Linear; or wants to start coding without claiming an issue (Linear ref is optional).
Draft post-deploy follow-up issues from a list of observations, then apply human-gate review before creating anything. Uses the propose-followups verb via linear.mjs. Every issue gets tech-debt + post-deploy + ai-suggested labels. Use when: engineer says "propose follow-ups", "log these after the deploy", "file follow-ups for that deploy", or /linear-propose-followups. Skip when: the work is a single obvious fix (use /linear-log-bug); or the observations don't come from a real post-deploy signal.
Show the Linear issue + uploaded plans + PRs attached to the current Claude Code session. Uses the session-info verb via linear.mjs. Use when: engineer asks "which Linear issue am I on", "what plans have I uploaded", "is this session linked", or /linear-session-info. Skip when: engineer is not using Linear at all.
Print a Linear Project's state: WIP per workflow state, milestone breakdown, link to the native Project Update. Uses the project-status verb via linear.mjs. Tech-lead hot path. Native Linear Project Updates come first — MCP fallback only if the native view is insufficient. Use when: tech lead or engineer says "project status", "how is X going", "show milestones for X", or /linear-status. Skip when: the ask is about a single issue (use the Linear UI or MCP) or about the whole team (no script covers that; use the Linear UI).
Scan the repo for TODO/FIXME/HACK comments and propose Linear tech-debt issues grouped by Area. Uses the triage-todos verb via linear.mjs. Human-gated for batches. Use when: engineer says "triage TODOs", "turn TODOs into issues", "clean up FIXMEs", or /linear-triage-todos. One-shot — run occasionally, not daily. Skip when: only a few markers exist (hand-edit them); or engineer wants to fix the markers directly without tracking.
Upload a Claude Code plan to the Linear issue linked to this session. Uses the upload-plan verb via linear.mjs. Plans are added as Linear documents and comments (full markdown) — never deleted. Use when: engineer says "upload this plan to Linear", "sync plan to TEAM-42", "push the plan file", or /linear-upload-plan. Also the auto-trigger for ExitPlanMode via the linear-plan-upload.sh hook. Skip when: session is not linked (script exits silently), or the plan is trivial enough that a comment would be noise — engineer's call.