Run any Skill in Manus with one click

Get Started

linear-create

Stars6

Forks0

UpdatedFebruary 9, 2026 at 03:15

Create a new issue in Linear. Use when the user says "create linear issue", "file linear ticket", or "add to linear".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

opmau

opmau/claude-code-framework

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	linear-create
description	Create a new issue in Linear. Use when the user says "create linear issue", "file linear ticket", or "add to linear".
argument-hint	<issue title>
user-invocable	true
allowed-tools	Bash, Read, Write, Glob, Grep
model	haiku

/linear-create — Create a Linear issue

Create a new issue in Linear using schpet/linear-cli.

Steps

Verify the Linear CLI is available:

linear --version 2>/dev/null || echo "LINEAR_CLI_MISSING"

Gather issue details. If $ARGUMENTS is provided, use it as the title. Determine:
- Title: short, descriptive (from arguments or ask)
- Team: which Linear team key (e.g., ENG) — check .linear.toml for default
- Priority: 1 (Urgent) / 2 (High) / 3 (Medium) / 4 (Low) / 0 (None)
- Labels: label names (e.g., bug, feature)
- Description: what needs to be done and why

Show the proposed issue to the user for confirmation before creating:

## Proposed Linear Issue

Title: <title>
Team: <team>
Priority: <priority>
Labels: <labels>
Description: <description>

Create this issue? (yes/no)

Create the issue in Linear:

linear issue create \
  -t "<title>" \
  -d "<description>" \
  --team "<team-key>" \
  --priority <priority-number> \
  --label "<label>" \
  --no-interactive

For multiple labels, repeat the flag: --label "bug" --label "high-priority"

Capture the returned issue ID (e.g., ENG-456).
Get the issue URL for reference:
```
linear issue url ENG-456
```

Report:

Created: ENG-456 — <title>
Priority: <priority>
URL: <linear-issue-url>

Run /linear-sync to update the local snapshot.

Arguments

No arguments: prompt for all details interactively
$ARGUMENTS: use as issue title, prompt for remaining details

Notes

Always confirm with the user before creating — creating issues is not reversible via the CLI
If creating from a bug fix or code change, include relevant file references in the description
Default to the team configured in .linear.toml if available, otherwise ask
Keep descriptions concise but include enough context for another developer
Use linear issue create --help to discover additional flags

More from this repository

same repository

fix-issue

opmau/claude-code-framework

Pick a bug from Linear, fix it test-first, verify, and update. Use when the user says "fix issue", "fix bug", "work on known issue", or "pick a bug".

2026-04-146

create-ticket

opmau/claude-code-framework

Create a new ticket for task tracking. Use when the user says "create ticket", "new ticket", or "track this".

2026-04-096

smoke-test

opmau/claude-code-framework

Diagnose an integration/E2E test log, classify failures by severity, and batch-create issues. Use when the user says "smoke test", "diagnose log", "triage test log", or provides a test log.

2026-04-096

linear-sync

opmau/claude-code-framework

Pull Linear issues and generate a local snapshot for quick reference. Use when the user says "sync linear", "pull linear issues", "update from linear", or "show my issues".

2026-02-096

linear-triage

opmau/claude-code-framework

Triage, prioritize, and groom Linear issues. Use when the user says "triage linear", "review inbox", "prioritize issues", "groom backlog", or "clean up issues".

2026-02-096

diagnose

opmau/claude-code-framework

Investigate a bug using structured differential diagnosis. Use when the user says "diagnose", "investigate this", "what's causing this", or "figure out why".

2026-02-096

/linear-create — Create a Linear issue

Create a new issue in Linear using schpet/linear-cli.

Steps

Verify the Linear CLI is available:

linear --version 2>/dev/null || echo "LINEAR_CLI_MISSING"

Gather issue details. If $ARGUMENTS is provided, use it as the title. Determine:

Title: short, descriptive (from arguments or ask)
Team: which Linear team key (e.g., ENG) — check .linear.toml for default
Priority: 1 (Urgent) / 2 (High) / 3 (Medium) / 4 (Low) / 0 (None)
Labels: label names (e.g., bug, feature)
Description: what needs to be done and why

Show the proposed issue to the user for confirmation before creating:

## Proposed Linear Issue

Title: <title>
Team: <team>
Priority: <priority>
Labels: <labels>
Description: <description>

Create this issue? (yes/no)

Create the issue in Linear:

linear issue create \
  -t "<title>" \
  -d "<description>" \
  --team "<team-key>" \
  --priority <priority-number> \
  --label "<label>" \
  --no-interactive

For multiple labels, repeat the flag: --label "bug" --label "high-priority"

Capture the returned issue ID (e.g., ENG-456).

Get the issue URL for reference:

linear issue url ENG-456

Report:

Created: ENG-456 — <title>
Priority: <priority>
URL: <linear-issue-url>

Run /linear-sync to update the local snapshot.

Arguments

No arguments: prompt for all details interactively

$ARGUMENTS: use as issue title, prompt for remaining details

Notes

Always confirm with the user before creating — creating issues is not reversible via the CLI

If creating from a bug fix or code change, include relevant file references in the description

Default to the team configured in .linear.toml if available, otherwise ask

Keep descriptions concise but include enough context for another developer

Use linear issue create --help to discover additional flags