What is create-linear-pr?

A command workflow that creates a Linear ticket, a Git branch, a commit, and a pull request. Linear is a project-management system, and a pull request is a request to review and merge code changes.

Use it after making code changes when you need to review the diff, create or use a Linear ticket, commit the work, and open a pull request.

It connects issue tracking and Git work so the ticket, branch, commit, and proposed merge follow one repeatable process.

create-linear-pr — Command by nodnarbnitram

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/nodnarbnitram/claude-code-extensions/create-linear-pr

Clone the repo

git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensions

Made for: Claude Code.

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 912 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00020	$0.00912
Opus 5	$0.00010	$0.00456
Sonnet 5	$0.00004	$0.00182
Haiku 4.5	$0.00002	$0.00091

Measured 2d ago against content hash e9b0482c67f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-linear-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/create-linear-pr.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Linear PR Workflow

Create a Linear ticket, branch from it, commit changes, and open a pull request.

Activate the linear skill first and use its wrapper scripts for all Linear operations. Do not call another Linear CLI directly from this workflow.

Context

Current git status: !git status --short
Current branch: !git branch --show-current
Staged changes: !git diff --cached --stat
Unstaged changes: !git diff --stat

Arguments

$1 - Team identifier (e.g., ICE-T)
$2 - Optional ticket title. If not provided, derive from the changes.

If team is missing, ask the user for it.

Prerequisites

Changes should already be made to files (staged or unstaged)
The linear skill must be available and its wrapper scripts must run successfully
gh CLI must be authenticated

Steps

Track these steps as TODOs and complete them one by one.

Validate arguments - Ensure $1 (team) is provided.
- If team is missing, ask the user for it.
Review changes - Analyze the context above to understand what will be committed.
- If no changes exist (no staged or unstaged files), stop and inform the user.
- Summarize the changes for the user.
- If $2 (title) not provided, derive a concise title from the changes.
Create Linear ticket - Use the linear skill wrapper script:
```
uv run .claude/skills/linear/scripts/create-ticket.py "<title from $2 or derived>" --team $1 --description "<auto-generated description>" --json
```
- Generate a meaningful description based on the changes being committed.
- Extract identifier, branchName, and url from the JSON response.

Create branch - Create and checkout the branch:

git checkout -b <branchName from Linear response>

Stage and commit - Stage relevant changes and commit:
```
git add <relevant files>
git commit -m "$(cat <<'EOF'
<TICKET-ID>: <title>

<detailed description of changes>
EOF
)"
```
- Always use HEREDOC for commit messages.
- Include the ticket ID prefix.

Read the full file on GitHub · 113 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 113 lines · 20 tokens per session scan A e9b0482c67f2

Subscribe to this mod's changes

create-linear-pr is a command published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 912 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Git and workflow Productivity

create-linear-pr

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Create Linear PR Workflow

Context

Arguments

Prerequisites

Steps

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement