Agent skill

Create Pull Request with Work Item ID

by makeplane in makeplane/plane

Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.

AGPL-3.0Auto-check passedDevelopment

Install Create Pull Request with Work Item ID

skills CLI
$ npx skills add makeplane/plane --skill create-pull-request -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install makeplane/plane create-pull-request --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/makeplane/plane.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/create-pull-request .claude/skills/create-pull-request && rm -rf skills-src

Use ~/.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/

Facts

Skill name
create-pull-request
GitHub stars
60k
Token cost
~824 tokens
SKILL.md length
408 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.

  • Works in 6 steps: Determine the base branch: Default to… → Gather context (in parallel) → Determine work item ID → …
  • Opening a PR for the branch you just finished
  • SKILL.md covers Workflow, Example Title, Guidelines and Common Mistakes
  • Calls git and gh

What it does

Before writing anything, the agent gathers context on the branch: git status, the diff stat and full diff against the base branch, the commit list, whether the branch tracks a remote, and the repository's .github/pull_request_template.md. The base branch defaults to preview unless you name another.

The work item ID comes from the branch name, for example SILO-1146 from a branch called chore/silo-1146-foo, and the agent asks you when the branch has none. The title starts with that ID, then a change type such as fix, feat, chore or refactor, then a short summary kept under 70 characters.

Each section of the template is filled in from the diff: a what-and-why description, ticked change types, concrete test scenarios, and references including linked issues and any Sentry links mentioned earlier. The screenshots section is left empty for you, a Claude Code session line is added, the branch is pushed with -u when it has no upstream, and gh pr create makes the PR and returns its URL.

When your agent uses it

  • Opening a PR for the branch you just finished
  • Writing a PR description that follows the repository's template
  • Prefixing a PR title with the Plane work item ID found in the branch name

Example prompts

  • “Create a pull request for this branch against preview.”
  • “Open a PR for the work on feat/web-1234-x using our PR template.”
  • “Push my branch and create the PR, the work item is SILO-1146.”

Requirements

  • Git with a remote and the GitHub CLI (`gh`)
  • A .github/pull_request_template.md file in the repository

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Determine the base branch: Default to preview unless the user specifies otherwise.
  2. Gather context (in parallel)
  3. Determine work item ID
  4. Draft the PR using the template from step 2
  5. Push and create (in parallel where possible)
  6. Return the PR URL to the user.

What it can do on your machine

Read from SKILL.md and the folder at commit 7466675. 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:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    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

Create Pull Request with Work Item ID loads about 824 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 408 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~824

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 makeplane/plane at commit 7466675, republished under its AGPL-3.0 licence (© makeplane). 408 words, ~824 tokens.

Download SKILL.mdSave it as .claude/skills/create-pull-request/SKILL.md (or your agent's skills folder).
name
create-pull-request
description
Use when creating a pull request for the current branch — gathers branch context, generates a PR description following the repo's pull_request_template.md, and creates the PR with a Plane work item ID prefix in the title.
user_invocable
true

Create PR

Create a pull request using the repo's PR template, a Plane work item ID as the title prefix, and a fully filled-out description based on the actual diff.

Workflow

  1. Determine the base branch: Default to preview unless the user specifies otherwise.

  2. Gather context (in parallel):

    • git status -s — check for uncommitted changes
    • git diff <base>...HEAD --stat — files changed
    • git log <base>...HEAD --oneline — all commits on the branch
    • git diff <base>...HEAD --no-color — full diff for understanding changes (if very large, focus on the most important files first)
    • git rev-parse --abbrev-ref --symbolic-full-name @{u} — check if branch tracks a remote
    • Read .github/pull_request_template.md from the repo root
  3. Determine work item ID:

    • Extract from branch name if it contains an identifier (e.g., chore/silo-1146-foo → SILO-1146, feat/web-1234-x → WEB-1234)
    • If not found in branch name, ask the user
  4. Draft the PR using the template from step 2:

    Title: [WORK-ITEM-ID] <type>: <concise summary> (under 70 chars)

    • Type reflects the change: fix, feat, chore, refactor, docs, perf, etc.

    Body: Fill in every section from the PR template based on the actual diff:

    • Description — Clear, concise summary of what the PR does and why. Focus on the "what" and "why", not line-by-line changes. Mention important implementation decisions.
    • Type of Change — Check the appropriate box(es): Bug fix, Feature, Improvement, Code refactoring, Performance improvements, Documentation update.
    • Screenshots and Media — Leave a placeholder: <!-- Add screenshots here -->
    • Test Scenarios — Suggest concrete scenarios grounded in the actual changes (e.g., "Navigate to project settings and verify the new toggle works"), not generic ones.
    • References — Include the work item ID, any linked issues the user mentions, and any Sentry issue links/IDs (e.g., SENTRY-ABC123 or Sentry URLs) referenced earlier in the conversation.

    Append a Claude Code session line at the bottom of the body.

  5. Push and create (in parallel where possible):

    • Push branch with -u if no upstream is set
    • Create PR via gh pr create using a HEREDOC for the body
  6. Return the PR URL to the user.

Show full SKILL.md (83 more words)Show less

Example Title

[SILO-1146] fix: allow relative URLs for configuration_url and improve app tile visibility

Guidelines

  • Keep the description concise but informative
  • Use bullet points when listing multiple changes
  • Focus on user-facing impact, not implementation details
  • Don't fabricate test scenarios that aren't relevant to the actual changes

Common Mistakes

  • Summarizing only the latest commit instead of all commits on the branch
  • Forgetting to check for an upstream before pushing
  • Using a work item ID format that doesn't match the branch convention
  • Wrapping the PR body in a code fence when passing it to gh pr create

© makeplane, AGPL-3.0. 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 .claude/skills/create-pull-request of makeplane/plane.

Open the folder on GitHubat commit 7466675

Compare with similar skills

Create Pull Request with Work Item ID 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.

Create Pull Request with Work Item ID compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Pull Request with Work Item ID this skillmakeplane/plane60k—~824Automated safety check: PassAGPL-3.0
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Creating Description For Gh PRredis/jedis12k—~838Automated safety check: PassMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Pascal Editor PR Openerpascalorg/editor25k—~619Automated safety check: PassMIT

Similar skills

  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated today
    DevelopmentAuto-check passed
  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Pascal Editor PR Opener

    pascalorg/editor

    Opens or refreshes a pull request on pascalorg/editor from the current branch, describing only what the branch's commits and diff actually contain.

    25k GitHub stars~619 tokensUpdated today
    DevelopmentAuto-check passed
  • Creates backports of a merged Ansible devel pull request onto the right stable branches by cherry-picking its merge commit onto new backport branches.

    71k GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed

More from makeplane/plane

  • React Doctor

    makeplane/plane

    Scans React code for lint, accessibility, bundle size and architecture issues, reports a health score and checks that changes do not lower it.

    60k GitHub starsUsed in 12 repos~657 tokens
    Auto-check passed
  • Git Branch Naming

    makeplane/plane

    Names a new Git branch with a type prefix, the lowercased work item ID and a short kebab-case description, so the ID can be extracted later from the branch name.

    60k GitHub stars~594 tokensUpdated yesterday
    Auto-check passed
  • Plane UI Translation

    makeplane/plane

    Sets the rules for translating and updating Plane's UI strings across locales: do-not-translate terms, plural forms, placeholders and AI translation review.

    60k GitHub stars~16k tokensUpdated yesterday
    Auto-check passed
  • Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.

    60k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Create Pull Request with Work Item ID

What does Create Pull Request with Work Item ID do?

Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff. md. The base branch defaults to preview unless you name another.

When should I use Create Pull Request with Work Item ID?

Create Pull Request with Work Item ID fits situations like: opening a PR for the branch you just finished; writing a PR description that follows the repository's template; prefixing a PR title with the Plane work item ID found in the branch name.

How do I install Create Pull Request with Work Item ID in Claude Code?

Run `npx skills add makeplane/plane --skill create-pull-request -a claude-code`. Or copy the skill folder (.claude/skills/create-pull-request in makeplane/plane) into .claude/skills/create-pull-request in your project. Claude Code loads it when a task matches its description.

How do I install Create Pull Request with Work Item ID in Codex?

Run `npx skills add makeplane/plane --skill create-pull-request -a codex`. Or copy the skill folder (.claude/skills/create-pull-request in makeplane/plane) into .agents/skills/create-pull-request in your project. Codex loads it when a task matches its description.

Can I use Create Pull Request with Work Item ID 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 makeplane/plane --skill create-pull-request -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-pull-request, .gemini/skills/create-pull-request, .github/skills/create-pull-request and .opencode/skills/create-pull-request in your project.

What does Create Pull Request with Work Item ID need to run?

Going by SKILL.md and its folder, Create Pull Request with Work Item ID needs the command-line tools its instructions call (git and gh). Our summary lists: Git with a remote and the GitHub CLI (`gh`); A .github/pull_request_template.md file in the repository.

Does Create Pull Request with Work Item ID access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Create Pull Request with Work Item ID 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 Create Pull Request with Work Item ID use?

Create Pull Request with Work Item ID is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create Pull Request with Work Item ID use?

About 824 tokens (SKILL.md is roughly 3.3k 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 Create Pull Request with Work Item ID?

Skills that share tags, products or a category with Create Pull Request with Work Item ID: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Creating Description For Gh PR (redis/jedis, 12k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Pull Request with Work Item ID?

makeplane (a GitHub organization) maintains it in makeplane/plane, which has 60,461 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.

Source: makeplane/plane on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.