Agent skill

Creating Pull Requests

MITAuto-check passedDevelopment

Install Creating Pull Requests

skills CLI

$ npx skills add makzimi/SwipingCards --skill creating-pull-requests -a claude-code

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

GitHub CLI

$ gh skill install makzimi/SwipingCards creating-pull-requests --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/makzimi/SwipingCards.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/creating-pull-requests .claude/skills/creating-pull-requests && 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 "creating-pull-requests" agent skill from https://github.com/makzimi/SwipingCards/tree/main/.claude/skills/creating-pull-requests into .claude/skills/creating-pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-pull-requests", 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/makzimi/SwipingCards/tree/main/.claude/skills/creating-pull-requests

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 makzimi/SwipingCards --skill creating-pull-requests -a codex

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

GitHub CLI

$ gh skill install makzimi/SwipingCards creating-pull-requests --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/makzimi/SwipingCards.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/creating-pull-requests .agents/skills/creating-pull-requests && 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 "creating-pull-requests" agent skill from https://github.com/makzimi/SwipingCards/tree/main/.claude/skills/creating-pull-requests into .agents/skills/creating-pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-pull-requests", 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 makzimi/SwipingCards --skill creating-pull-requests -a cursor

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

GitHub CLI

$ gh skill install makzimi/SwipingCards creating-pull-requests --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/makzimi/SwipingCards.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/creating-pull-requests .cursor/skills/creating-pull-requests && 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 "creating-pull-requests" agent skill from https://github.com/makzimi/SwipingCards/tree/main/.claude/skills/creating-pull-requests into .cursor/skills/creating-pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-pull-requests", 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/makzimi/SwipingCards.git --path .claude/skills/creating-pull-requests

--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 makzimi/SwipingCards --skill creating-pull-requests -a gemini-cli

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

GitHub CLI

$ gh skill install makzimi/SwipingCards creating-pull-requests --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/makzimi/SwipingCards.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/creating-pull-requests .gemini/skills/creating-pull-requests && 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 "creating-pull-requests" agent skill from https://github.com/makzimi/SwipingCards/tree/main/.claude/skills/creating-pull-requests into .gemini/skills/creating-pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-pull-requests", 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 makzimi/SwipingCards creating-pull-requests

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 makzimi/SwipingCards --skill creating-pull-requests -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/makzimi/SwipingCards.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/creating-pull-requests .github/skills/creating-pull-requests && 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 "creating-pull-requests" agent skill from https://github.com/makzimi/SwipingCards/tree/main/.claude/skills/creating-pull-requests into .github/skills/creating-pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-pull-requests", 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 makzimi/SwipingCards --skill creating-pull-requests -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 makzimi/SwipingCards creating-pull-requests --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/makzimi/SwipingCards.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/creating-pull-requests .opencode/skills/creating-pull-requests && 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 "creating-pull-requests" agent skill from https://github.com/makzimi/SwipingCards/tree/main/.claude/skills/creating-pull-requests into .opencode/skills/creating-pull-requests/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "creating-pull-requests", 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: creating-pull-requests
GitHub stars: 114
Token cost: ~2.2k tokens
SKILL.md length: 950 words
Files: 1
Skills in repo: 1
Repo updated: Jul 13, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Works in 7 steps: Decide whether to branch first → Understand what the branch does → Determine the base branch → …
Submit a PR / pull request / merge request
SKILL.md covers Step 1: Decide whether to…, Step 2: Understand what the…, Step 3: Determine the base… and Step 4: Push the branch, plus 4 more sections
Calls git and gh

What it does

Creating Pull Requests is an agent skill from makzimi/SwipingCards. Create a well-formed pull request from the current branch — handles branch naming, base-branch detection (including stacked PRs), a clear title and description, pushing, and opening the PR with the gh CLI. Use this whenever the user wants to open, create, raise, or submit a PR / pull request / merge request, or asks to "put this up for review", "ship this branch", or "make a PR" — even if they don't spell out every step. Prefer this skill over ad-hoc git pushes so PRs stay consistent and reviewable.

Its SKILL.md is about 2.2k 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: A swipeable card deck for Jetpack Compose — flick the top card and it cycles to the back. The licence is MIT.

When your agent uses it

Submit a PR / pull request / merge request
Asks to put this up for review
Ship this branch
Make a PR — even if they dont spell out every step

Example prompts

“put this up for review”
“ship this branch”
“make a PR”
“/creating-pull-requests”

Workflow steps

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

Decide whether to branch first
Understand what the branch does
Determine the base branch
Push the branch
Compose the title
Compose the description
Confirm, then create

What it can do on your machine

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

Creating Pull Requests loads about 2.2k tokens when it runs. Until then it costs about 132 tokens; SKILL.md has 950 words of instructions outside code blocks.

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

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 makzimi/SwipingCards at commit 9075a23, republished under its MIT licence (© makzimi). 950 words, ~2,176 tokens.

Download SKILL.mdSave it as .claude/skills/creating-pull-requests/SKILL.md (or your agent's skills folder).

name: creating-pull-requests
description: Create a well-formed pull request from the current branch — handles branch naming, base-branch detection (including stacked PRs), a clear title and description, pushing, and opening the PR with the gh CLI. Use this whenever the user wants to open, create, raise, or submit a PR / pull request / merge request, or asks to "put this up for review", "ship this branch", or "make a PR" — even if they don't spell out every step. Prefer this skill over ad-hoc git pushes so PRs stay consistent and reviewable.

Creating Pull Requests

A pull request is read by a human who wasn't there when you wrote the code. The goal of this skill is a PR whose title and description let a reviewer understand what changed and why in under a minute, targeting the right base branch, without you having to remember every step each time.

Work through the steps below in order. Most are quick; the ones that matter most are getting the base branch right and writing a description that explains the why, not just the what.

Step 1: Decide whether to branch first

Look at the current branch (git branch --show-current).

If it's the repo's default branch (main, master, or develop), or the user explicitly asked to "create a branch and a PR", create a new branch first — you should not open a PR directly from a shared trunk.
If you're already on a working branch with commits, use it as-is.

When creating a branch, follow the repo's existing convention if there is one (scan git branch -a for the prevailing style). Absent a convention, a type-prefixed, kebab-case name reads well and sorts sensibly:

Prefix	When	Example
`feature/`	New functionality	`feature/infinite-deck`
`fix/`	Bug fix	`fix/cart-crash-on-empty-promo`
`refactor/`	Restructuring without behavior change	`refactor/extract-deck-state`
`chore/`	Tooling, deps, build, CI	`chore/bump-compose-bom`
`docs/`	Documentation only	`docs/api-migration-notes`
`test/`	Adding or updating tests	`test/reconciler-edge-cases`

For a large feature or epic, add a segment to express the hierarchy — e.g. feature/gifting/add-send-page. This also feeds stacked-PR detection in Step 3.

Step 2: Understand what the branch does

Read the actual change, don't guess: the commit subjects (`git log --oneline

<base>..HEAD`), the file stat (`git diff --stat <base>..HEAD`), and skim the diff
for anything surprising. You need a real grasp of the change to write a title and
description that are true to it.

If you can't reconstruct the why — the problem being solved or the goal — from the commits and diff, ask the user rather than inventing a motivation. A confident-but-wrong rationale is worse than a question.

Step 3: Determine the base branch

The PR targets the branch it was forked from. Getting this wrong sends dozens of unrelated commits into the wrong review, so resolve it deliberately in this order:

User-specified — if the user named a base branch, use it.
Stacked / cascading PRs — if the current branch name has 3+ segments (e.g. feature/gifting/add-send-page), strip the last segment and check whether that parent branch exists on the remote:
bash
```
git ls-remote --heads origin "feature/gifting"
```
If it exists, it's almost certainly the intended base — each branch in a stack targets its parent, not the trunk.

Repo default branch — otherwise, target the repository's default branch. Detect it rather than assuming main:

bash

gh repo view --json defaultBranchRef --jq .defaultBranchRef.name 2>/dev/null \
  || git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||' \
  || echo main

Confirm — show the resolved base branch to the user before creating the PR, especially for a stacked PR where the base isn't the trunk. A one-line "Base: feature/gifting — correct?" is enough.

Step 4: Push the branch

Make sure the branch is on the remote (git push -u origin <branch> if it isn't). The PR can't be opened otherwise.

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

Step 5: Compose the title

A good title is a single scannable line that says what the change accomplishes. Match the repo's existing PR/commit-title convention if it has one (check recent merged PRs or git log). Absent a convention, this default reads cleanly:

Format: [Type] <Topic>. <Imperative summary> — Topic is optional; include it only when there's a meaningful feature/epic area (often the middle segment of a hierarchical branch name).

Type	When
`[Feature]`	New functionality
`[Fix]`	Bug fix
`[Refactor]`	Restructuring, no behavior change
`[Chore]`	Tooling, deps, build, CI
`[Docs]`	Documentation
`[Test]`	Tests

Examples:

Input: branch feature/gifting/add-send-page, adds a gift-sending screen Output: [Feature] Gifting. Add gift-sending page

Input: branch fix/cart-crash-on-empty-promo, fixes a null deref on empty promo Output: [Fix] Cart. Fix crash on empty promo state

Input: branch refactor/migrate-di-to-ksp, swaps annotation processing backend Output: [Refactor] Migrate DI from kapt to KSP

Keep the summary imperative ("Add", "Fix", "Migrate"), not past tense.

Step 6: Compose the description

Write for the reviewer, in plain, direct English — the tone of a good teammate explaining their change, not a formal report.

If the repo has a PR template (.github/pull_request_template.md or .github/PULL_REQUEST_TEMPLATE/), use it and fill in each section. Teams rely on their template; don't replace it with your own structure.

Otherwise, use this structure:

markdown

## What & why

<1–2 sentences on the problem or goal, then what you did at a high level.>

## Changes

- <High-level, reviewer-facing bullets. Group by intent, not by file.>

## Testing

<How you verified it: commands run and their result, or manual steps. "N/A" if
genuinely nothing to run.>

## Screenshots / video

<For any UI change. Otherwise omit this section or write "N/A".>

Good example:

markdown

## What & why

Users couldn't find caffeine-free drinks, so they kept asking support. Added a
"Caffeine-free" filter to the menu.

## Changes

- Added the filter checkbox to the menu filter sheet
- Threaded the new filter through MenuFeature's state and query
- Covered the filtering logic with unit tests

## Testing

`./gradlew :menu:test` — all green. Verified on device that toggling the filter
narrows the list and clearing it restores everything.

## Screenshots / video

_N/A_

Avoid these:

Listing every changed file — that's what the diff is for. Describe intent.
Formal filler ("In the scope of this task, the following was accomplished…"). Say it plainly.
Skipping the why. The motivation is the one thing the diff can't show, so it's the most valuable thing you can add.
Padding a small change into a long template. Match the length to the change.

Step 7: Confirm, then create

Show the user the resolved base branch, the title, and the description, and wait for approval or edits. This is cheap and prevents a wrong-base or wrong-framing PR that then needs to be edited or reopened.

Once approved, prefer the gh CLI over any GitHub MCP tool — check it's ready with gh auth status. Create the PR, passing the body via a here-doc so formatting survives:

bash

gh pr create --base <base-branch> --title "<title>" --body-file - <<'EOF'
<body>
EOF

Add --draft if the user wants a draft. If gh isn't installed or authenticated, fall back to the GitHub MCP create_pull_request tool.

Print the PR URL when it's created. If the change touches UI and you couldn't attach screenshots, remind the user to add them.

Quick rules

Never open a PR from a shared trunk (main/master/develop) — branch first.
Resolve the base branch deliberately; support stacked PRs; confirm before creating.
Explain the why before the what; keep the length proportional to the change.
Use the repo's PR template and title convention when they exist.
Push before creating; confirm title, description, and base with the user first.

Files

Just SKILL.md in .claude/skills/creating-pull-requests of makzimi/SwipingCards.

Open the folder on GitHubat commit 9075a23

Compare with similar skills

Creating Pull Requests 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.

Creating Pull Requests compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Creating Pull Requests this skillmakzimi/SwipingCards	114	—	~2.2k	Automated safety check: Pass	MIT	2 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	today
Pull Request Title and Body Writeropeninterpreter/openinterpreter	69k	2 repos	~1.1k	Automated safety check: Pass	Apache-2.0	today

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 today
DevelopmentAuto-check passed

Works with

Questions about Creating Pull Requests

What does Creating Pull Requests do?

Create a well-formed pull request from the current branch — handles branch naming, base-branch detection (including stacked PRs), a clear title and description, pushing, and opening the PR with the…. Creating Pull Requests is an agent skill from makzimi/SwipingCards. Create a well-formed pull request from the current branch — handles branch naming, base-branch detection (including stacked PRs), a clear title and description, pushing, and opening the PR with the gh CLI.

When should I use Creating Pull Requests?

Creating Pull Requests fits situations like: submit a PR / pull request / merge request; asks to put this up for review; ship this branch; make a PR — even if they dont spell out every step.

How do I install Creating Pull Requests in Claude Code?

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

How do I install Creating Pull Requests in Codex?

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

Can I use Creating Pull Requests 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 makzimi/SwipingCards --skill creating-pull-requests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/creating-pull-requests, .gemini/skills/creating-pull-requests, .github/skills/creating-pull-requests and .opencode/skills/creating-pull-requests in your project.

What does Creating Pull Requests need to run?

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

Does Creating Pull Requests 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 Creating Pull Requests 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 Creating Pull Requests use?

Creating Pull Requests 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 Creating Pull Requests use?

About 2.2k tokens (SKILL.md is roughly 8.7k 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 Creating Pull Requests?

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

makzimi (a GitHub user) maintains it in makzimi/SwipingCards, which has 114 GitHub stars. The repository was last updated on July 13, 2026.

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

Install Creating Pull Requests

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

Creating Pull Requests

Step 1: Decide whether to branch first

Step 2: Understand what the branch does

Step 3: Determine the base branch

Step 4: Push the branch

Step 5: Compose the title

Step 6: Compose the description

Step 7: Confirm, then create

Quick rules

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 Creating Pull Requests