Agent skill

Create PR

by go-to-k in go-to-k/cdkd

Run /verify-pr checks, then create a GitHub PR if all pass. An agent skill from go-to-k/cdkd.

Apache-2.0Auto-check passedDevelopment

Install Create PR

skills CLI
$ npx skills add go-to-k/cdkd --skill create-pr -a claude-code

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

GitHub CLI
$ gh skill install go-to-k/cdkd create-pr --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/go-to-k/cdkd.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/create-pr .claude/skills/create-pr && 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-pr
GitHub stars
144
Token cost
~873 tokens
SKILL.md length
465 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
Apache-2.0

At a glance

Run /verify-pr checks, then create a GitHub PR if all pass. An agent skill from go-to-k/cdkd.

  • Works in 8 steps: Ensure on a feature branch with the… → Run /verify-pr — typecheck, lint, build,… → Ensure changes are committed and pushed → …
  • Tasks that involve Pull requests
  • SKILL.md covers Steps and Important
  • Calls git and gh

What it does

Create PR is an agent skill from go-to-k/cdkd. Run /verify-pr checks, then create a GitHub PR if all pass. Automates the full flow from quality checks to PR creation.

Its SKILL.md is about 870 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, Git, Amazon Web Services and AWS CloudFormation. The repository describes itself as: Drop-in CDK CLI for existing CDK apps — up to 15x faster deploys via direct AWS SDK calls instead of CloudFormation. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/create-pr”

Workflow steps

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

  1. Ensure on a feature branch with the right cwd
  2. Run /verify-pr — typecheck, lint, build, tests, CI, docs consistency, leftover resources. If any check fails, stop and report.
  3. Ensure changes are committed and pushed
  4. Check if PR already exists for the current branch
  5. Gather PR context
  6. Draft PR title and body
  7. Create PR
  8. Report the PR URL.

What it can do on your machine

Read from SKILL.md and the folder at commit 8a604fd. 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 PR loads about 873 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 465 words of instructions outside code blocks.

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

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 go-to-k/cdkd at commit 8a604fd, republished under its Apache-2.0 licence (© go-to-k). 465 words, ~873 tokens.

Download SKILL.mdSave it as .claude/skills/create-pr/SKILL.md (or your agent's skills folder).
name
create-pr
description
Run /verify-pr checks, then create a GitHub PR if all pass. Automates the full flow from quality checks to PR creation.
argument-hint
[--base <branch>]

Create PR

Run all quality checks and create a GitHub PR if everything passes.

Steps

  1. Ensure on a feature branch with the right cwd:

    • git branch --show-current — check current branch
    • Multi-worktree pre-flight: if the current branch is main (or master), also run git worktree list --porcelain and check whether any other worktree is on a non-main branch. If yes, surface that explicitly:
      git worktree list --porcelain | awk '/^worktree /{wt=$2} /^branch refs\/heads\//{b=substr($0,index($0,"refs/heads/")+11); if (b!="main" && b!="master") print wt " on branch " b}'
      The user almost certainly meant to run /create-pr from that worktree — every later git / gh pr view call defaults to cwd, so running from the parent worktree on main reports "no PR found for branch 'main'" while a feature branch with commits sits elsewhere. Stop and ask whether to proceed in the listed worktree (offer cd <path>) before falling through to "create a new branch".
    • If on main and no other worktrees have non-main branches, ask the user for a branch name and create it: git checkout -b <branch-name>.
    • Branch naming convention: feat/, fix/, refactor/, docs/, chore/ prefix.
    • Later steps assume cwd is that worktree; if the user defers the cd, abort rather than guess.
  2. Run /verify-pr — typecheck, lint, build, tests, CI, docs consistency, leftover resources. If any check fails, stop and report.

  3. Ensure changes are committed and pushed:

    • git status — commit any uncommitted changes that belong to this branch's work
    • git push -u origin <branch> — ensure remote is up to date
  4. Check if PR already exists for the current branch:

    • gh pr view --json number,url -q '.url' 2>/dev/null
    • If a PR exists, update its title/body (see /verify-pr step 12), report the URL, and stop — skip steps 5–8
  5. Gather PR context:

    • git log main...HEAD --oneline — all commits in this branch
    • git diff main...HEAD --stat — changed files summary
    • Determine base branch (default: main, overridable with --base)
  6. Draft PR title and body:

    • Title: concise, under 70 characters
    • Base the title and body on the actual diff (git diff main...HEAD), not just commit messages — commit messages may reflect intermediate iterations that were later reverted
    • Always write the PR title and body in English
    • Body format:
      ## Summary
      - bullet points of what changed and why
      
      ## Test plan
      - [ ] Unit tests pass (N files, M tests)
      - [ ] Integration test: <which ones were run, if any>
      - [ ] Documentation updated
  7. Create PR:

    bash
    gh pr create --title "..." --body "$(cat <<'EOF'
    ...
    EOF
    )"
  8. Report the PR URL.

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

Important

  • Do NOT create a PR if any /verify-pr check fails
  • Always push before creating the PR
  • If the branch has no commits ahead of main, warn and stop
  • Verify a PR update landed, with gh pr view. A wrong --body-file path or a shell-eaten backtick writes the wrong body silently. gh api repos/{owner}/{repo}/pulls/{number} -X PATCH -F body=@<file> is the better spelling for a body full of backticks, since @<file> is read verbatim

© go-to-k, Apache-2.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-pr of go-to-k/cdkd.

Open the folder on GitHubat commit 8a604fd

Compare with similar skills

Create PR 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 PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create PR this skillgo-to-k/cdkd144—~873Automated safety check: PassApache-2.0
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

  • 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
  • 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
  • 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
  • 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 yesterday
    DevelopmentAuto-check passed
  • 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 go-to-k/cdkd

All 14 skills in this repo
  • Hunt Bugs

    go-to-k/cdkd

    Proactively hunt for cdkd bugs by deploying real CDK apps that exercise common-but-untested AWS resources, configs, and CloudFormation notations against real AWS, then fix what breaks.

    144 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Use Cdkd

    go-to-k/cdkd

    Build the current cdkd checkout and use it from another CDK project.

    144 GitHub stars~669 tokensUpdated today
    Auto-check passed
  • Verify PR

    go-to-k/cdkd

    Comprehensive PR readiness check before merge. An agent skill from go-to-k/cdkd.

    144 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Work Issues

    go-to-k/cdkd

    Work through already-filed GitHub issues (typically the bug-hunt's output) end to end — triage safely, pick as many FILE-DISJOINT issues as the run can carry, claim each on the issue before starting…

    144 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Cdkd

    go-to-k/cdkd

    Install cdkd and use it safely from an AWS CDK project. An agent skill from go-to-k/cdkd.

    144 GitHub stars~6.7k tokensUpdated today
    Auto-check: notes
  • Run Integ

    go-to-k/cdkd

    Run integration tests (deploy + destroy) against real AWS. An agent skill from go-to-k/cdkd.

    144 GitHub stars~5.8k tokensUpdated today
    Auto-check passed

Categories

Questions about Create PR

What does Create PR do?

Run /verify-pr checks, then create a GitHub PR if all pass. An agent skill from go-to-k/cdkd. Create PR is an agent skill from go-to-k/cdkd. Run /verify-pr checks, then create a GitHub PR if all pass.

When should I use Create PR?

Create PR fits situations like: tasks that involve Pull requests.

How do I install Create PR in Claude Code?

Run `npx skills add go-to-k/cdkd --skill create-pr -a claude-code`. Or copy the skill folder (.claude/skills/create-pr in go-to-k/cdkd) into .claude/skills/create-pr in your project. Claude Code loads it when a task matches its description.

How do I install Create PR in Codex?

Run `npx skills add go-to-k/cdkd --skill create-pr -a codex`. Or copy the skill folder (.claude/skills/create-pr in go-to-k/cdkd) into .agents/skills/create-pr in your project. Codex loads it when a task matches its description.

Can I use Create PR 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 go-to-k/cdkd --skill create-pr -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-pr, .gemini/skills/create-pr, .github/skills/create-pr and .opencode/skills/create-pr in your project.

What does Create PR need to run?

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

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

Create PR is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create PR use?

About 873 tokens (SKILL.md is roughly 3.5k 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 PR?

Skills that share tags, products or a category with Create PR: 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 PR?

go-to-k (a GitHub user) maintains it in go-to-k/cdkd, which has 144 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 9, 2026.

Source: go-to-k/cdkd on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.