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.
Create and update Linear issues via CLI (write operations)
Teams using linear-issues-write should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
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
linear-issue-generator
Linear Issue Generator - Auto-activating skill for Enterprise Workflows. Triggers on: linear issue generator, linear issue generator Part of the Enterprise Workflows skill category.
scanning-for-data-privacy-issues
This skill enables Claude to automatically scan code and configuration files for potential data privacy vulnerabilities using the data-privacy-scanner plugin. It identifies sensitive data exposure, compliance violations, and other privacy-related risks. Use this skill when the user requests to "scan for data privacy issues", "check privacy compliance", "find PII leaks", "identify GDPR violations", or needs a "privacy audit" of their codebase. The skill is most effective when used on projects involving personal data, financial information, or health records.
cursor-indexing-issues
Troubleshoot Cursor codebase indexing: stuck indexing, empty search, @codebase failures, and performance issues. Triggers on "cursor indexing", "cursor index", "@codebase not working", "cursor search broken", "indexing stuck".
scanning-for-accessibility-issues
This skill enables Claude to perform comprehensive accessibility audits. It uses the accessibility-test-scanner plugin to identify WCAG 2.1/2.2 compliance issues, validate ARIA attributes, check keyboard navigation, and assess screen reader compatibility. Use this skill when the user requests an accessibility scan, audit, or compliance check, or when terms like "WCAG", "ARIA", "screen reader", "accessibility testing", or "a11y" are mentioned. It provides actionable insights for improving web application accessibility.
document-writer
多风格文档写作技能。支持乔木、小红书、Dankoe、微信公众号、Twitter等5种写作风格。Claude 根据内容智能选择风格，按规范撰写文章。
reddit-post-writer
Master authentic Reddit content generator using emotion-first, phased architecture. Creates posts that sound genuinely human through cognitive state simulation, not just rule-following. Use when the user asks to write a Reddit post, create Reddit content, or needs help with Reddit engagement. Includes adversarial committee review, Claude-ism detection, and interactive refinement workflow.
write-coding-standards-from-file
Write a coding standards document for a project using the coding styles from the file(s) and/or folder(s) passed as arguments in the prompt.
my-issues
List my issues in the current repository
gen-specs-as-issues
This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.
create-github-issues-for-unmet-specification-requirements
Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.
create-github-issues-feature-from-implementation-plan
Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.
pr-writer
ALWAYS use this skill when creating or updating pull requests — never create or edit a PR directly without it. Follows Sentry conventions for PR titles, descriptions, and issue references. Trigger on any create PR, open PR, submit PR, make PR, update PR title, update PR description, edit PR, push and create PR, prepare changes for review task, or request for a PR writer.