Skip to content

About

Agent Skill: turn a Linear issue ID into a branch, implementation and pull request.

Topics

Resources

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

1 Commit

Folders and files

Repository files navigation

linear-issue-to-pr

An Agent Skill that turns a Linear issue ID into finished work. Say work on ENG-42 and the agent:

  1. fetches the issue and its comments from Linear,
  2. creates or switches to the issue's branch (Linear's gitBranchName),
  3. implements the change and runs the project's checks,
  4. commits, pushes and opens a pull request that closes the issue.

It never merges, and it does not restate the ticket back to you before starting: the issue in Linear is the spec.

Requirements

  • An agent with shell and git access, such as Claude Code, running inside a git repository with an origin remote.
  • The Linear MCP server connected:
    claude mcp add --transport http linear-server https://mcp.linear.app/mcp
    then run /mcp inside Claude Code to authenticate.
  • Optional: the GitHub CLI (gh auth login) to open PRs automatically. Without it you get a ready-to-click compare URL.

Install

Claude Code plugin marketplace

/plugin marketplace add mbarradev-debug/linear-issue-to-pr
/plugin install linear-issue-to-pr@mbarradev-skills

skills CLI (Claude Code, Cursor, Codex and other agents)

npx skills add mbarradev-debug/linear-issue-to-pr

Manual

git clone https://github.com/mbarradev-debug/linear-issue-to-pr
cp -r linear-issue-to-pr/skills/linear-issue-to-pr ~/.claude/skills/

Usage

work on ENG-42
get issue DBO-1104
resuelve la issue ENG-42

Before touching code it prints a single status line:

[ENG-42] Add dark mode toggle · Type: feature · Priority: High · Status: Todo

and ends with a completion checklist, the branch name and the PR link.

Behavior worth knowing

Topic What the skill does
Branch Uses Linear's gitBranchName; new branches start from origin/<default-branch>, detected automatically (not hard-coded main).
Safety Stops if the working tree has unrelated uncommitted changes, if git fetch fails, or if it ends up on the wrong branch. Never stashes or discards your work.
Commits Conventional format, e.g. feat(eng-42): add dark mode toggle. Stages files by path, not git add -A. Your git hooks run normally.
Attribution No Co-Authored-By trailers or "Generated with" footers, unless the repo's own rules (CONTRIBUTING.md, CLAUDE.md, AGENTS.md) require AI disclosure.
Merge Never. You review and merge the PR.

To turn attribution off globally in Claude Code as well, add this to ~/.claude/settings.json:

{ "attribution": { "commits": false, "pullRequests": false } }

Repository layout

.claude-plugin/
  marketplace.json      Claude Code marketplace catalog
  plugin.json           plugin manifest
skills/linear-issue-to-pr/
  SKILL.md              workflow and rules
  references/
    git-workflow.md     branch setup and close-the-cycle procedures
    plan-templates.md   per-type planning templates

License

MIT

About

Agent Skill: turn a Linear issue ID into a branch, implementation and pull request.

Topics

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors