Agent skill

Create PR

by PanAchy in PanAchy/copilot-arewecooked

Create PRs with titles and bodies that produce accurate release notes.

MITAuto-check passedDevelopment

Install Create PR

skills CLI

$ npx skills add PanAchy/copilot-arewecooked --skill create-pr -a claude-code

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

GitHub CLI

$ gh skill install PanAchy/copilot-arewecooked 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/PanAchy/copilot-arewecooked.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/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/

Paste into Claude Code

Install the "create-pr" agent skill from https://github.com/PanAchy/copilot-arewecooked/tree/develop/.agents/skills/create-pr into .claude/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", 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

$skill-installer install https://github.com/PanAchy/copilot-arewecooked/tree/develop/.agents/skills/create-pr

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

skills CLI

$ npx skills add PanAchy/copilot-arewecooked --skill create-pr -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install PanAchy/copilot-arewecooked create-pr --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PanAchy/copilot-arewecooked.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/create-pr .agents/skills/create-pr && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "create-pr" agent skill from https://github.com/PanAchy/copilot-arewecooked/tree/develop/.agents/skills/create-pr into .agents/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", 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.

skills CLI

$ npx skills add PanAchy/copilot-arewecooked --skill create-pr -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install PanAchy/copilot-arewecooked create-pr --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PanAchy/copilot-arewecooked.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/create-pr .cursor/skills/create-pr && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "create-pr" agent skill from https://github.com/PanAchy/copilot-arewecooked/tree/develop/.agents/skills/create-pr into .cursor/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", 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

$ gemini skills install https://github.com/PanAchy/copilot-arewecooked.git --path .agents/skills/create-pr

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add PanAchy/copilot-arewecooked --skill create-pr -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install PanAchy/copilot-arewecooked create-pr --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PanAchy/copilot-arewecooked.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/create-pr .gemini/skills/create-pr && rm -rf skills-src

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

Paste into Gemini CLI

Install the "create-pr" agent skill from https://github.com/PanAchy/copilot-arewecooked/tree/develop/.agents/skills/create-pr into .gemini/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", 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.

GitHub CLI

$ gh skill install PanAchy/copilot-arewecooked create-pr

Installs 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).

skills CLI

$ npx skills add PanAchy/copilot-arewecooked --skill create-pr -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/PanAchy/copilot-arewecooked.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/create-pr .github/skills/create-pr && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "create-pr" agent skill from https://github.com/PanAchy/copilot-arewecooked/tree/develop/.agents/skills/create-pr into .github/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", 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.

skills CLI

$ npx skills add PanAchy/copilot-arewecooked --skill create-pr -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install PanAchy/copilot-arewecooked create-pr --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/PanAchy/copilot-arewecooked.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/create-pr .opencode/skills/create-pr && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "create-pr" agent skill from https://github.com/PanAchy/copilot-arewecooked/tree/develop/.agents/skills/create-pr into .opencode/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", 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: create-pr
GitHub stars: 137
Token cost: ~840 tokens
SKILL.md length: 431 words
Files: 1
Skills in repo: 1
Repo updated: Jun 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Create PRs with titles and bodies that produce accurate release notes.

Works in 7 steps: Create short-lived feature branches from… → Open normal work PRs from feature… → Prefer squash merge for feature →… → …
Opening a pull request
SKILL.md covers Rules, PR title format, PR body format and Before creating a feature →…, plus 3 more sections
Calls git, gh and npm

What it does

Create PR is an agent skill from PanAchy/copilot-arewecooked. Create PRs with titles and bodies that produce accurate release notes. Use when opening a pull request, merging to develop or main, or when user says "open a PR", "create a PR", "ready to merge", or "ship it".

Its SKILL.md is about 840 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 Git. The repository describes itself as: Estimate your GitHub Copilot AI-credit cost in preparation for June 1st. The licence is MIT.

When your agent uses it

Opening a pull request
Merging to develop
User says open a PR

Example prompts

“open a PR”
“create a PR”
“ready to merge”
“/create-pr”

Workflow steps

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

Create short-lived feature branches from develop for all work.
Open normal work PRs from feature branches into develop.
Prefer squash merge for feature → develop PRs. The PR title becomes one clean Conventional Commit on develop.
Open release PRs from develop into main when ready to ship.
Merge release PRs with a merge commit, not squash, so release-please sees the individual Conventional Commits accumulated on develop.
The release PR body becomes useful release context, but release-please changelog entries come from commits merged to main.
Use fix(...) for release-affecting fixes, including broken publish/release automation. Do not use ci(...) if the change must trigger a…

What it can do on your machine

Read from SKILL.md and the folder at commit 1e89480. 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
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, gh and npm, 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 840 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 431 words of instructions outside code blocks.

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

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 PanAchy/copilot-arewecooked at commit 1e89480, republished under its MIT licence (© PanAchy). 431 words, ~840 tokens.

Download SKILL.mdSave it as .claude/skills/create-pr/SKILL.md (or your agent's skills folder).

name: create-pr
description: Create PRs with titles and bodies that produce accurate release notes. Use when opening a pull request, merging to develop or main, or when user says "open a PR", "create a PR", "ready to merge", or "ship it".

Create PR

Rules

Create short-lived feature branches from develop for all work.
Open normal work PRs from feature branches into develop.
Prefer squash merge for feature → develop PRs. The PR title becomes one clean Conventional Commit on develop.
Open release PRs from develop into main when ready to ship.
Merge release PRs with a merge commit, not squash, so release-please sees the individual Conventional Commits accumulated on develop.
The release PR body becomes useful release context, but release-please changelog entries come from commits merged to main.
Use fix(...) for release-affecting fixes, including broken publish/release automation. Do not use ci(...) if the change must trigger a release.

PR title format

<type>(<scope>): <summary of all changes>

Pick the highest-impact type: feat > fix > refactor > test > docs > chore.

PR body format

## What changed

- <change 1>
- <change 2>
- <change 3>

## Context

<1-2 sentences on why>

## Test plan

- [ ] <how to verify>

Before creating a feature → develop PR

Run git fetch origin.
Confirm current branch is a feature branch, not main or develop: git branch --show-current.
Run git diff origin/develop...HEAD --name-status to see actual changed files in the PR.
Run git diff origin/develop...HEAD -- <file> to understand actual content changes.
Synthesize the title and body from the diff, not from commit headlines alone.
Verify npm run build && npm test passes.
Push the branch: git push -u origin <branch>.
Create PR: gh pr create --base develop --head <branch> --title "<title>" --body "<body>".
After creating PR, run gh pr diff <number> --name-only and gh pr view <number> --json files,title,body to confirm body matches actual changed files.

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

Before creating a develop → main release PR

Run git fetch origin.
Run git diff origin/main...origin/develop --name-status to see actual release contents.
Run git log --oneline origin/main..origin/develop to review Conventional Commits that release-please will see after merge.
Verify release PR body summarizes the diff, not stale branch history.
Create PR: gh pr create --base main --head develop --title "chore(release): merge develop into main" --body "<body>".
Merge with a merge commit, not squash.

Title quality check

Would a user reading the changelog understand what changed?
Does it cover all user-visible changes, not just the first commit?
Is the type correct? (feat = user-visible feature, fix = bug, chore = internal)
No period at the end. No trailing punctuation.

Bad vs Good

Bad: feat: updates (vague) Bad: fix: typo in readme when the branch also adds tests and error handling (understates) Bad: feat: add error handling, tests, --version flag, npm publish, CONTRIBUTING.md (too long, use body)

Good: feat: add error handling, tests, and npm publish workflow (concise, accurate scope) Good: fix: handle malformed JSONL in source parsers (specific, covers the real fix)

Files

Just SKILL.md in .agents/skills/create-pr of PanAchy/copilot-arewecooked.

Open the folder on GitHubat commit 1e89480

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
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Create PR this skillPanAchy/copilot-arewecooked	137	—	~840	Automated safety check: Pass	MIT	4 mo ago
Finishing a Development Branchobra/superpowers	297k	5 repos	~1.9k	Automated safety check: Pass	MIT	yesterday
Contributor-First PR MergeHKUDS/OpenHarness	16k	1 repos	~847	Automated safety check: Pass	MIT	4 mo ago
Open Code Review CLIalibaba/open-code-review	46k	—	~3.1k	Automated safety check: Pass	Apache-2.0	yesterday
Create Pull Requestcline/cline	70k	1 repos	~1.6k	Automated safety check: Pass	Apache-2.0	yesterday
Pull Request Title and Body Writeropeninterpreter/openinterpreter	69k	2 repos	~1.1k	Automated safety check: Pass	Apache-2.0	4 days ago

Similar skills

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.
297k GitHub starsUsed in 5 repos~1.9k tokens
DevelopmentAuto-check passed
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
Open Code Review CLI
alibaba/open-code-review
Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.
46k GitHub stars~3.1k tokensUpdated yesterday
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
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
86k GitHub stars~1.4k tokensUpdated yesterday
DevelopmentAuto-check passed

Works with

Questions about Create PR

What does Create PR do?

Create PRs with titles and bodies that produce accurate release notes. Create PR is an agent skill from PanAchy/copilot-arewecooked. Create PRs with titles and bodies that produce accurate release notes.

When should I use Create PR?

Create PR fits situations like: opening a pull request; merging to develop; user says open a PR.

How do I install Create PR in Claude Code?

Run `npx skills add PanAchy/copilot-arewecooked --skill create-pr -a claude-code`. Or copy the skill folder (.agents/skills/create-pr in PanAchy/copilot-arewecooked) 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 PanAchy/copilot-arewecooked --skill create-pr -a codex`. Or copy the skill folder (.agents/skills/create-pr in PanAchy/copilot-arewecooked) 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 PanAchy/copilot-arewecooked --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, gh and npm).

Does Create PR access the network?

SKILL.md contains no URLs. Its commands use git, gh and npm, 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 MIT 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 840 tokens (SKILL.md is roughly 3.4k 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: Finishing a Development Branch (obra/superpowers, 297k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Open Code Review CLI (alibaba/open-code-review, 46k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create PR?

PanAchy (a GitHub user) maintains it in PanAchy/copilot-arewecooked, which has 137 GitHub stars. The repository was last updated on June 7, 2026.

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

Install Create PR

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Create PR

Rules

PR title format

PR body format

Before creating a feature → develop PR

Before creating a develop → main release PR

Title quality check

Bad vs Good

Files

Compare with similar skills

Similar skills

Finishing a Development Branch

Contributor-First PR Merge

Open Code Review CLI

Create Pull Request

Pull Request Title and Body Writer

Understand Diff Analysis

Related

Questions about Create PR