Draft Pull Request Creator
wordpress-mobile/WordPress-Android
Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.
A skill your agent uses when creating a Linear issue from the current coding context, or when the user invokes /linear-issue.
Install Linear Issue
$ npx skills add ReviewStage/stage-cli --skill linear-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ReviewStage/stage-cli linear-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ReviewStage/stage-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/linear-issue .claude/skills/linear-issue && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "linear-issue" agent skill from https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/linear-issue into .claude/skills/linear-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/linear-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ReviewStage/stage-cli --skill linear-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ReviewStage/stage-cli linear-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ReviewStage/stage-cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/linear-issue .agents/skills/linear-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linear-issue" agent skill from https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/linear-issue into .agents/skills/linear-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ReviewStage/stage-cli --skill linear-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ReviewStage/stage-cli linear-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ReviewStage/stage-cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/linear-issue .cursor/skills/linear-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "linear-issue" agent skill from https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/linear-issue into .cursor/skills/linear-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ReviewStage/stage-cli.git --path .agents/skills/linear-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ReviewStage/stage-cli --skill linear-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ReviewStage/stage-cli linear-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ReviewStage/stage-cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/linear-issue .gemini/skills/linear-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "linear-issue" agent skill from https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/linear-issue into .gemini/skills/linear-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ReviewStage/stage-cli linear-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ReviewStage/stage-cli --skill linear-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ReviewStage/stage-cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/linear-issue .github/skills/linear-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "linear-issue" agent skill from https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/linear-issue into .github/skills/linear-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ReviewStage/stage-cli --skill linear-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ReviewStage/stage-cli linear-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ReviewStage/stage-cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/linear-issue .opencode/skills/linear-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "linear-issue" agent skill from https://github.com/ReviewStage/stage-cli/tree/main/.agents/skills/linear-issue into .opencode/skills/linear-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
linear-issue- GitHub stars
- 274
- Token cost
- ~2k tokens
- SKILL.md length
- 878 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when creating a Linear issue from the current coding context, or when the user invokes /linear-issue.
- Works in 6 steps: CONTEXT → SEARCH → TEAMS → …
- Creating a Linear issue from the current coding context
- SKILL.md covers Workflow, Step 1: CONTEXT, Step 2: SEARCH and Step 3: TEAMS, plus 4 more sections
- Calls gh; reaches linear.app
What it does
Linear Issue is an agent skill from ReviewStage/stage-cli. Use when creating a Linear issue from the current coding context, or when the user invokes /linear-issue. Infers team, priority, status, and relationships from conversation context, working directory, and git branch.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Git workflow. It works with Linear. The repository describes itself as: A viewer for reviewing local code changes in small individual chapters. Works with any AI agent. The licence is MIT.
When your agent uses it
- Creating a Linear issue from the current coding context
- The user invokes /linear-issue
Example prompts
- “/linear-issue”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 59b977b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
linear.app
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Linear Issue loads about 2k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 878 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ReviewStage/stage-cli at commit 59b977b, republished under its MIT licence (© ReviewStage). 878 words, ~1,993 tokens.
Download SKILL.mdSave it as
.claude/skills/linear-issue/SKILL.md (or your agent's skills folder).- name
- linear-issue
- description
- Use when creating a Linear issue from the current coding context, or when the user invokes /linear-issue. Infers team, priority, status, and relationships from conversation context, working directory, and git branch.
- metadata.internal
- true
Creating Linear Issues
Single-pass workflow: gather context, search existing issues, infer fields informed by what's already filed, create issue.
Workflow
1. CONTEXT → Gather signals: args, conversation, directory, git branch
2. SEARCH → list_issues broadly to find duplicates, related issues, and inform inference
3. TEAMS → list_teams to get available teams (informed by search results)
4. INFER → Determine title, description, team, priority, status, labels, project, links, relationships
5. CREATE → create_issue with inferred fields + relationships
6. REPORT → Display created issue summaryStep 1: CONTEXT
Gather all available signals:
- Args: Description provided after
/linear-issue— primary signal - Conversation: If no args, summarize current discussion as issue description
- Directory: Current working directory/package (e.g.
packages/ai/suggests AI-related team) - Git branch: Branch name often encodes feature/bug context
Step 2: SEARCH
Search existing issues before anything else — what's already filed informs every downstream decision including team selection.
- Call
list_issueswith keywords extracted from the context (args, conversation summary, branch name) - Search broadly across teams — no team filter yet, since search results may reveal the correct team
- Collect results into three buckets:
| Bucket | Criteria | Used for |
|---|---|---|
| Duplicates | Same intent and scope as new issue | Stop and warn user |
| Related | Same area, overlapping context | Relationship inference in Step 4 |
| Informative | Same team/area but different scope | Team/priority/status inference in Step 4 |
If a strong duplicate is found (same intent and scope): STOP. Do not proceed to Step 4. Report the existing issue:
Possible duplicate found — did not create.
Existing: TEAM-99 "Add retry logic to extraction agent"
Status: In Progress | Assignee: @charles
URL: https://linear.app/...
Reply if you still want to create a new issue.Step 3: TEAMS
Call list_teams → get all workspace teamsUse search results from Step 2 to guide matching — if related issues belong to a specific team, that's strong evidence for the correct team.
Step 4: INFER
Use context from Step 1, search results from Step 2, and team list from Step 3 to determine all fields.
Team
- Primary signal: which team do related/informative issues belong to?
- Secondary signal: directory/package name fuzzy-matched against team names from Step 3
- Fallback: broadest team
Priority
| Signal | Priority |
|---|---|
| "ASAP", "urgent", "blocking", "broken", "critical", "P0", "production down" | 1 (Urgent) |
| "soon", "important", "next few days", "high priority", "P1" | 2 (High) |
| No urgency signal / default | 3 (Normal) |
| "low priority", "nice to have", "when we get to it", "P3", "minor" | 4 (Low) |
Also consider: what priority are related issues set to? Match the neighborhood.
Status
| Signal | Status |
|---|---|
| "needs discussion", "RFC", "should we", "not sure if", "explore", "maybe" | Backlog |
| Default / clear actionable task | Todo |
| "I'm working on", "currently", "in progress", "started" | In Progress |
Title
Extract or generate a concise title in imperative form, under 80 characters.
Description
Format as markdown. Include:
- What the issue is about
- Context: branch name, relevant file/package, conversation summary
- Any acceptance criteria apparent from context
Labels
Infer labels from context and search results:
- From description: "bug"/"broken"/"error" → bug label, "feature"/"add"/"new" → feature label, "refactor"/"tech debt"/"cleanup" → tech-debt label
- From related issues: If related issues share a common label, apply it to the new issue too
- Call
list_issue_labelswith the inferred team to verify labels exist before applying. Only use labels that actually exist in the workspace.
Project
- If related issues from Step 3 belong to a project, add the new issue to the same project
- If the conversation or args explicitly mention a project name, use that
- Otherwise, leave unset
Links
Add traceability links back to the development context:
- If on a branch with an open PR, link to the PR URL
- If the conversation references a specific file or commit, link to it on GitHub
- Use
links: [{url, title}]format
Show full SKILL.md (377 more words)Show less
Relationships
Analyze related issues from Step 3:
Sub-issue (parentId) — New issue is a specific task within a broader existing issue.
Example: "fix retry in extraction agent" is a sub-issue of "improve chapter generation reliability"
Parent — New issue encompasses existing smaller issues. After creating, call update_issue on each child to set their parentId.
Blocking / Blocked-by (blocks / blockedBy) — Use when:
- Explicit dependency language: "this blocks X", "can't do Y until this is done"
- Technical dependency: "migrate DB schema" blocks "add new column"
Related (relatedTo) — Same area, shared context, but neither blocks the other.
Step 5: CREATE
Call create_issue with:
| Field | Value |
|---|---|
title | Inferred title (imperative, <80 chars) |
description | Markdown description with context |
team | Matched team name |
priority | Numeric: 1=Urgent, 2=High, 3=Normal, 4=Low |
state | Status name: "Backlog", "Todo", "In Progress" |
labels | Array of label names inferred from context |
project | Project name (if related issues share a project) |
links | Array of {url, title} linking to PR/branch/commit |
parentId | Parent issue identifier (if sub-issue) |
blocks | Array of issue identifiers this blocks |
blockedBy | Array of issue identifiers blocking this |
relatedTo | Array of related issue identifiers |
If this issue is a parent of existing issues, after creation call update_issue on each child to set parentId.
Step 6: REPORT
Created: TEAM-123 "Add retry logic to chapter generation"
Team: Product | Priority: Normal | Status: Todo
Labels: bug, ai-pipeline | Project: Chapter Gen V2
Parent: TEAM-100 "Improve chapter generation reliability"
Related: TEAM-98 "Audit error handling in AI pipeline"
Links: PR #42 "feat: add retry logic"
URL: https://linear.app/...Common Mistakes
| Mistake | Fix |
|---|---|
| Inferring fields before searching existing issues | Always search first — existing issues inform team, priority, and relationships |
| Creating without checking duplicates | Step 3 catches duplicates before any inference work |
| Setting priority too high by default | Default is Normal (3), only escalate with clear urgency signals |
| Guessing team instead of looking up | Always call list_teams and match against actual teams |
| Searching only within one team | Search broadly first — related issues may be in a different team |
| Forgetting to set relationships | Check related bucket from Step 3 for parent/blocking/related |
| Using IDs instead of names for state | create_issue accepts state names directly ("Backlog", "Todo") |
| Skipping description context | Always include branch, directory, and conversation context |
| Creating parent without updating children | After creating a parent issue, call update_issue on children |
| Applying labels that don't exist | Call list_issue_labels to verify labels exist before using them |
| Ignoring project from related issues | If related issues share a project, add the new issue to it |
| Not linking back to PR/branch | Always check for an open PR with gh pr view and link it |
© ReviewStage, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/linear-issue of ReviewStage/stage-cli.
Open the folder on GitHubat commit 59b977b
Compare with similar skills
Linear Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Linear Issue this skillReviewStage/stage-cli | 274 | — | ~2k | Automated safety check: Pass | MIT | |
| Draft Pull Request Creatorwordpress-mobile/WordPress-Android | 3.2k | — | ~881 | Automated safety check: Notes | GPL-2.0 | |
| Managing Git Workflowhashintel/hash | 1.7k | — | ~1.2k | Automated safety check: Pass | AGPL-3.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT |
Similar skills
Managing Git Workflow
hashintel/hash
Git and pull-request workflow for HASH, including conditional Linear conventions and merge-queue diagnostics.
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
More from ReviewStage/stage-cli
All 10 skills in this repoFixing CI
ReviewStage/stage-cli
A skill your agent uses when CI is failing on a branch and you need to diagnose failures from GitHub, fix them locally with iterative verification, and re-push clean commits.
Fixing PR Comments
ReviewStage/stage-cli
A skill your agent uses when a pull request has unresolved review comments that need to be addressed, or when asked to fix PR feedback
Iterate PR
ReviewStage/stage-cli
A skill your agent uses when a PR is open and the user wants to autonomously monitor and fix PR review comments, CI failures, and rebase conflicts on a recurring loop, or when asked to…
Quality Review
ReviewStage/stage-cli
A skill your agent uses when reviewing code changes against AGENTS.md implementation quality standards, or when asked to do an implementation quality review
Rebase Origin Main
ReviewStage/stage-cli
A skill your agent uses when rebasing the current branch onto origin/main, including resolving merge conflicts along the way
Trade Off
ReviewStage/stage-cli
Use at any stage — planning, before implementing, or reviewing code that's already written — to surface high-level trade-offs that could significantly simplify the work.
Related
Works with
Categories
Questions about Linear Issue
What does Linear Issue do?
A skill your agent uses when creating a Linear issue from the current coding context, or when the user invokes /linear-issue. Linear Issue is an agent skill from ReviewStage/stage-cli. Use when creating a Linear issue from the current coding context, or when the user invokes /linear-issue.
When should I use Linear Issue?
Linear Issue fits situations like: creating a Linear issue from the current coding context; the user invokes /linear-issue.
How do I install Linear Issue in Claude Code?
Run `npx skills add ReviewStage/stage-cli --skill linear-issue -a claude-code`. Or copy the skill folder (.agents/skills/linear-issue in ReviewStage/stage-cli) into .claude/skills/linear-issue in your project. Claude Code loads it when a task matches its description.
How do I install Linear Issue in Codex?
Run `npx skills add ReviewStage/stage-cli --skill linear-issue -a codex`. Or copy the skill folder (.agents/skills/linear-issue in ReviewStage/stage-cli) into .agents/skills/linear-issue in your project. Codex loads it when a task matches its description.
Can I use Linear Issue in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ReviewStage/stage-cli --skill linear-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linear-issue, .gemini/skills/linear-issue, .github/skills/linear-issue and .opencode/skills/linear-issue in your project.
What does Linear Issue need to run?
Going by SKILL.md and its folder, Linear Issue needs the command-line tools its instructions call (gh).
Does Linear Issue access the network?
SKILL.md names 1 domain. In commands or code: linear.app; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Linear Issue safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Linear Issue use?
Linear Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Linear Issue use?
About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Linear Issue?
Skills that share tags, products or a category with Linear Issue: Draft Pull Request Creator (wordpress-mobile/WordPress-Android, 3.2k stars), Managing Git Workflow (hashintel/hash, 1.7k stars), Finishing a Development Branch (obra/superpowers, 296k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Linear Issue?
ReviewStage (a GitHub organization) maintains it in ReviewStage/stage-cli, which has 274 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 7, 2026.
Source: ReviewStage/stage-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.