linear-issues-write
Create and update Linear issues via CLI (write operations)
Best use case
linear-issues-write is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Create and update Linear issues via CLI (write operations)
Create and update Linear issues via CLI (write operations)
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "linear-issues-write" skill to help with this workflow task. Context: Create and update Linear issues via CLI (write operations)
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/linear-issues-write/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How linear-issues-write Compares
| Feature / Agent | linear-issues-write | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create and update Linear issues via CLI (write operations)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## Overview CLI tools for creating and updating Linear issues. Requires `LINEAR_API_KEY` set in `<git-root>/.env` or exported in the environment. ## Prerequisites - [bun](https://bun.sh) runtime installed - `LINEAR_API_KEY` set in `<git-root>/.env` or environment ## Commands ### Create Issue ```bash bun .opencode/skill/linear-issues-write/create-issue.js --title "..." --team <team> [options] ``` **Required:** - `--title <title>` - Issue title - `--team <name>` - Team name (e.g., Engineering) **Options:** - `--description <text>` - Issue description - `--assignee <name>` - Assignee name - `--priority <0-4>` - Priority: 0=none, 1=urgent, 2=high, 3=medium, 4=low - `--labels <labels>` - Comma-separated labels (e.g., "Bug,SOC2") - `--project <name>` - Project name - `--json` - Output as JSON **Examples:** ```bash bun .opencode/skill/linear-issues-write/create-issue.js --title "Fix login bug" --team Engineering --priority 2 bun .opencode/skill/linear-issues-write/create-issue.js --title "New feature" --team Engineering --labels "Feature" --assignee "John Adams" bun .opencode/skill/linear-issues-write/create-issue.js --title "Security fix" --team Engineering --project "Monticello" --priority 1 ``` --- ### Update Issue ```bash bun .opencode/skill/linear-issues-write/update-issue.js <issue-id> [options] ``` **Arguments:** - `issue-id` - Issue identifier (e.g., ENG-123) or UUID **Options:** - `--title <title>` - New title - `--description <text>` - New description - `--status <status>` - New status (e.g., "In Progress", "Done") - `--assignee <name>` - New assignee (use "none" to unassign) - `--priority <0-4>` - New priority - `--labels <labels>` - Replace all labels - `--add-labels <labels>` - Add labels without removing existing - `--project <name>` - Set project (use "none" to remove) - `--json` - Output as JSON **Examples:** ```bash bun .opencode/skill/linear-issues-write/update-issue.js ENG-123 --status "In Progress" bun .opencode/skill/linear-issues-write/update-issue.js ENG-123 --assignee "Thomas Jefferson" --priority 2 bun .opencode/skill/linear-issues-write/update-issue.js ENG-123 --add-labels "Bug,Urgent" bun .opencode/skill/linear-issues-write/update-issue.js ENG-123 --assignee none ``` --- ## Notes - Team, user, and label names are resolved automatically (case-insensitive) - Use `--json` flag for machine-readable output suitable for scripting - All commands support `--help` for detailed usage information
Related Skills
prd-doc-writer
Write and iteratively refine PRD/需求文档 with a story-driven structure and strict staged confirmations (journey map alignment, per-story single-point confirmation, final generation gate). Use when the user asks to 梳理/撰写/完善 PRD、需求文档、用户故事、验收标准,并希望用 ASCII 线框图与 Mermaid(流程图/状态图/时序图)来减少歧义、共同完成文档。
svelte-code-writer
CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
writer
Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation with LibreOffice Writer.
wiki-page-writer
Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems.
seo-content-writer
Writes SEO-optimized content based on provided keywords and topic briefs. Creates engaging, comprehensive content following best practices. Use PROACTIVELY for content creation tasks.
linear-claude-skill
Manage Linear issues, projects, and teams
linear-automation
Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.
typescript-write
Write TypeScript and JavaScript code following Metabase coding standards and best practices. Use when developing or refactoring TypeScript/JavaScript code.
docs-write
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
clojure-write
Guide Clojure and ClojureScript development using REPL-driven workflow, coding conventions, and best practices. Use when writing, developing, or refactoring Clojure/ClojureScript code.
gws-docs-write
Google Docs: Append text to a document.
reporting-issues
Use this skill when you need to report on a troubleshooting session