New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Create Pull Request

by haru in haru/redmine_ai_helper

Create a pull request from the current branch. An agent skill from haru/redmine_ai_helper.

MITAuto-check passedDevelopment

Install Create Pull Request

skills CLI
$ npx skills add haru/redmine_ai_helper --skill create-pull-request -a claude-code

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

GitHub CLI
$ gh skill install haru/redmine_ai_helper 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/haru/redmine_ai_helper.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
106
Token cost
~1.5k tokens
SKILL.md length
754 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Create a pull request from the current branch. An agent skill from haru/redmine_ai_helper.

  • Works in 2 steps: Identify Current Branch → Determine Branch Type
  • You want to open a PR
  • SKILL.md covers User Input, Procedure, Release Branch Workflow… and Feature/Fix Branch Workflow…, plus 1 more section
  • Calls git and gh

What it does

Create Pull Request is an agent skill from haru/redmine_ai_helper. Create a pull request from the current branch. Use when you want to open a PR, submit changes, or create a pull request. Handles release branches (release/) and feature/fix branches differently, setting the correct base branch, title, description, and labels automatically.

Its SKILL.md is about 1.5k 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 Pull requests. It works with GitHub and Git. The repository describes itself as: A Redmine plugin that adds AI agents, MCP Server, smart completion, and vector search. The licence is MIT.

When your agent uses it

  • You want to open a PR
  • Create a pull request

Example prompts

  • “/create-pull-request”

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. Identify Current Branch
  2. Determine Branch Type

What it can do on your machine

Read from SKILL.md and the folder at commit 3cd87d6. 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 loads about 1.5k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 754 words of instructions outside code blocks.

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

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 haru/redmine_ai_helper at commit 3cd87d6, republished under its MIT licence (© haru). 754 words, ~1,477 tokens.

Download SKILL.mdSave it as .claude/skills/create-pull-request/SKILL.md (or your agent's skills folder).
name
create-pull-request
description
Create a pull request from the current branch. Use when you want to open a PR, submit changes, or create a pull request. Handles release branches (release/**) and feature/fix branches differently, setting the correct base branch, title, description, and labels automatically.
argument-hint
Optional: additional context or instructions for the PR
user-invocable
true
disable-model-invocation
false

Create Pull Request

Create a pull request from the current branch with appropriate title, description, base branch, and labels.

User Input

text
$ARGUMENTS

Consider any additional context from the user input before proceeding.

Procedure

Step 1: Identify Current Branch

Run git branch --show-current to get the current branch name.

Step 2: Determine Branch Type

Check if the branch name starts with release/:

  • Release branch (release/**): follow the Release Branch workflow below
  • All other branches: follow the Feature/Fix Branch workflow below

Release Branch Workflow (release/**)

Base Branch

main

Title

Extract the version from the branch name.

  • Branch release/1.2.3 → title: Release 1.2.3
  • Format: Release <version>
Description

Use the same text as the title. No additional details needed.

Release <version>
Labels

None — do not add any labels.

Create PR

Use the GitHub MCP tool (mcp_github_mcp_se_create_pull_request) as the primary method. If unavailable, fall back to gh pr create:

gh pr create --base main --title "Release <version>" --body "Release <version>"

Feature/Fix Branch Workflow (non-release branches)

Base Branch

develop

Title

If the branch is a Spec Kit branch (branch name matches pattern used by speckit, e.g., feature/NNN-* or follows the speckit branch convention):

  1. Locate the corresponding spec.md file under .specify/ (e.g., .specify/<branch-folder>/spec.md)
  2. Read the spec.md and derive a concise English title from the feature description
  3. Title should be imperative and descriptive, e.g., Add vector model profile support

If the branch is NOT a Spec Kit branch:

  1. Run git log develop..HEAD --oneline to list commits on this branch
  2. Run git diff develop...HEAD --stat to see changed files
  3. Derive a concise, imperative English title summarizing the changes
  4. Example: Fix issue summary cache invalidation

Determine whether this PR fixes or implements an existing GitHub issue. Look for issue references in these sources, in order:

  1. User input ($ARGUMENTS): e.g., #123, issue 123, or a GitHub issue URL.
  2. Commit messages: run git log develop..HEAD --format=%B and look for #123, Fixes #123, Closes #123, or GitHub issue URLs.
  3. Spec Kit artifacts (Spec Kit branches only): look for GitHub issue URLs or #123 references in the feature's spec.md (e.g., in the input/description section).
  4. Branch name: only a pattern explicitly naming an issue, such as issue-123, issue/123, or fix/#123. Do not treat the Spec Kit sequential prefix (e.g., 062- in 062-optional-temperature) as an issue number — it is a feature counter, not an issue ID.

For each candidate number, verify it is an existing issue (not a pull request) in this repository using the GitHub MCP tool (issue_read) or gh issue view <number> --json number,title,state. Discard candidates that do not exist or are pull requests.

If no reference is found but the changes clearly address a known problem, you may search open issues (GitHub MCP search_issues or gh issue list --search "<keywords>" --state open). Only link a search result if it clearly matches the changes; if uncertain, ask the user to confirm rather than guessing, since a wrong link can auto-close an unrelated issue.

If no related issue is identified, skip the issue line in the description.

Show full SKILL.md (263 more words)Show less
Description

Run git diff develop...HEAD --stat and git log develop..HEAD --oneline to understand the changes.

Write a short English description using a bullet list:

markdown
## Changes

- <concise description of change 1>
- <concise description of change 2>
- ...

Keep each bullet to one line. Focus on what changed and why, not implementation details.

If a related issue was identified, put it at the top of the description using a GitHub closing keyword so the PR is linked to the issue:

markdown
Fixes #<issue-number>

## Changes

- ...
  • Use Fixes #N for bug fixes and Closes #N for features/enhancements.
  • For multiple issues, put each on its own line (e.g., Fixes #12 and Fixes #34).
  • If the PR only partially addresses the issue, use Related to #N instead so the issue is not auto-closed.
Labels

Analyze the changes and select one or more labels from:

LabelWhen to use
enhancementNew feature or improvement
bugBug fix
documentationDocs-only change (README, YARD, locales)

Select all that apply. If a label does not exist in the repository, skip it rather than failing.

Create PR

Use the GitHub MCP tool (mcp_github_mcp_se_create_pull_request) as the primary method to create the PR. If the MCP tool is unavailable, fall back to gh pr create:

gh pr create \
  --base develop \
  --title "<title>" \
  --body "<description>" \
  --label "<label1>" \
  --label "<label2>"

Error Handling

  • If git log or git diff returns empty (branch has no commits ahead of base), inform the user there is nothing to PR.
  • If the spec.md file cannot be found for a Spec Kit branch, fall back to deriving the title from git commits.
  • If label creation fails (label does not exist), omit that label and proceed.
  • If the PR already exists for this branch, report the existing PR URL instead of creating a duplicate.

© haru, 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 .claude/skills/create-pull-request of haru/redmine_ai_helper.

Open the folder on GitHubat commit 3cd87d6

Compare with similar skills

Create Pull Request 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 compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Pull Request this skillharu/redmine_ai_helper106—~1.5kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0
PR Review State Fetchprisma/orm48k—~767Automated safety check: PassApache-2.0
Creating Description For Gh PRredis/jedis12k—~838Automated safety check: PassMIT

Similar skills

  • 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.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    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

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • PR Review State Fetch

    prisma/orm

    Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated today
    DevelopmentAuto-check passed

  • Creating Description For Gh PR

    redis/jedis

    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

  • Create Pull Request with Work Item ID

    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.

    61k GitHub stars~824 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from haru/redmine_ai_helper

All 21 skills in this repo

  • Commit

    haru/redmine_ai_helper

    Stage the current changes and create a git commit with a properly formatted English message.

    106 GitHub stars~1.1k tokensUpdated today
    Auto-check: notes

  • Create Release Branch

    haru/redmine_ai_helper

    Create a release branch for a given version. An agent skill from haru/redmine_ai_helper.

    106 GitHub stars~599 tokensUpdated today
    Auto-check passed

  • Qlty Check

    haru/redmine_ai_helper

    Code quality checks, formatting, and metrics via qlty CLI. An agent skill from haru/redmine_ai_helper.

    106 GitHub starsUsed in 2 repos~628 tokens
    Auto-check passed

  • Redmine Playwright Login

    haru/redmine_ai_helper

    Connect to the running Redmine instance and log in via the Playwright MCP browser, using REDMINEPLAYRIGHTURL/REDMINEPLAYRIGHTUSER/REDMINEPLAYRIGHTPASSWORD environment variables.

    106 GitHub stars~796 tokensUpdated today
    Auto-check passed

  • Recreate Test DB

    haru/redmine_ai_helper

    Recreate the Redmine test database from scratch (delete db/schema.rb and db/redmine.sqlite3test, then run core and plugin migrations with RAILSENV=test).

    106 GitHub stars~364 tokensUpdated today
    Auto-check passed

  • Create Release Notes

    haru/redmine_ai_helper

    Generate Redmine.org release notes from a GitHub release tag.

    106 GitHub stars~768 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Create Pull Request

What does Create Pull Request do?

Create a pull request from the current branch. An agent skill from haru/redmine_ai_helper. Create Pull Request is an agent skill from haru/redmine_ai_helper. Create a pull request from the current branch.

When should I use Create Pull Request?

Create Pull Request fits situations like: you want to open a PR; create a pull request.

How do I install Create Pull Request in Claude Code?

Run `npx skills add haru/redmine_ai_helper --skill create-pull-request -a claude-code`. Or copy the skill folder (.claude/skills/create-pull-request in haru/redmine_ai_helper) 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 in Codex?

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

Can I use Create Pull Request 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 haru/redmine_ai_helper --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 need to run?

Going by SKILL.md and its folder, Create Pull Request needs the command-line tools its instructions call (git and gh).

Does Create Pull Request 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 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 use?

Create Pull Request 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 Create Pull Request use?

About 1.5k tokens (SKILL.md is roughly 5.9k 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?

Skills that share tags, products or a category with Create Pull Request: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and PR Review State Fetch (prisma/orm, 48k 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?

haru (a GitHub user) maintains it in haru/redmine_ai_helper, which has 106 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.

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