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.
Create or update a pull request for pgtrickle. An agent skill from trickle-labs/pg-trickle.
Install Create Pull Request
$ npx skills add trickle-labs/pg-trickle --skill create-pull-request -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install trickle-labs/pg-trickle create-pull-request --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/trickle-labs/pg-trickle.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/create-pull-request .claude/skills/create-pull-request && rm -rf skills-srcUse ~/.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/
Install the "create-pull-request" agent skill from https://github.com/trickle-labs/pg-trickle/tree/main/.github/skills/create-pull-request into .claude/skills/create-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pull-request", 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 install https://github.com/trickle-labs/pg-trickle/tree/main/.github/skills/create-pull-requestType 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.
$ npx skills add trickle-labs/pg-trickle --skill create-pull-request -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install trickle-labs/pg-trickle create-pull-request --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/trickle-labs/pg-trickle.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/create-pull-request .agents/skills/create-pull-request && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-pull-request" agent skill from https://github.com/trickle-labs/pg-trickle/tree/main/.github/skills/create-pull-request into .agents/skills/create-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pull-request", 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.
$ npx skills add trickle-labs/pg-trickle --skill create-pull-request -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install trickle-labs/pg-trickle create-pull-request --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/trickle-labs/pg-trickle.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/create-pull-request .cursor/skills/create-pull-request && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "create-pull-request" agent skill from https://github.com/trickle-labs/pg-trickle/tree/main/.github/skills/create-pull-request into .cursor/skills/create-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pull-request", 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 https://github.com/trickle-labs/pg-trickle.git --path .github/skills/create-pull-request--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add trickle-labs/pg-trickle --skill create-pull-request -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install trickle-labs/pg-trickle create-pull-request --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/trickle-labs/pg-trickle.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/create-pull-request .gemini/skills/create-pull-request && rm -rf skills-srcUse ~/.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/
Install the "create-pull-request" agent skill from https://github.com/trickle-labs/pg-trickle/tree/main/.github/skills/create-pull-request into .gemini/skills/create-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pull-request", 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.
$ gh skill install trickle-labs/pg-trickle create-pull-requestInstalls 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).
$ npx skills add trickle-labs/pg-trickle --skill create-pull-request -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/trickle-labs/pg-trickle.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/create-pull-request .github/skills/create-pull-request && rm -rf skills-srcUse ~/.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/
Install the "create-pull-request" agent skill from https://github.com/trickle-labs/pg-trickle/tree/main/.github/skills/create-pull-request into .github/skills/create-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pull-request", 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.
$ npx skills add trickle-labs/pg-trickle --skill create-pull-request -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install trickle-labs/pg-trickle create-pull-request --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/trickle-labs/pg-trickle.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/create-pull-request .opencode/skills/create-pull-request && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "create-pull-request" agent skill from https://github.com/trickle-labs/pg-trickle/tree/main/.github/skills/create-pull-request into .opencode/skills/create-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pull-request", 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-pull-request- GitHub stars
- 147
- Token cost
- ~1.1k tokens
- SKILL.md length
- 406 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Create or update a pull request for pgtrickle. An agent skill from trickle-labs/pg-trickle.
- Works in 6 steps: Gather Context → Choose a Title → Write the PR Description → …
- : opening a new PR
- SKILL.md covers When to Use, Prerequisites, Procedure and Branch Rules, plus 1 more section
- Calls gh, just and git
What it does
Create Pull Request is an agent skill from trickle-labs/pg-trickle. Create or update a pull request for pgtrickle. Use when: opening a new PR, fixing a garbled PR description, updating an existing PR body, or preparing a PR after finishing a feature or fix. Handles the safe body-file workflow to avoid Unicode corruption.
Its SKILL.md is about 1.1k 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. The repository describes itself as: A PostgreSQL 18+ extension for streaming tables with incremental view maintenance, powered by differential dataflow in Rust. The licence is Apache-2.0.
When your agent uses it
- : opening a new PR
- Fixing a garbled PR description
- Updating an existing PR body
- Preparing a PR after finishing a feature
Example prompts
- “/create-pull-request”
Requirements
- Python 3
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 101c5d3. 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:
ghjustgitpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, 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.1k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 406 words of instructions outside code blocks.
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 trickle-labs/pg-trickle at commit 101c5d3, republished under its Apache-2.0 licence (© trickle-labs). 406 words, ~1,057 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 or update a pull request for pg_trickle. Use when: opening a new PR, fixing a garbled PR description, updating an existing PR body, or preparing a PR after finishing a feature or fix. Handles the safe body-file workflow to avoid Unicode corruption.
- argument-hint
- Branch name or short description of the change (e.g. fix/scheduler-race)
Create Pull Request
Safe, Unicode-correct workflow for creating or updating GitHub pull requests in
the pg_trickle repository. Never use shell heredocs or echo for PR
bodies — they silently corrupt Unicode (math symbols, em-dashes, etc.) and
can pick up stale content from a previous session.
When to Use
- Opening a new pull request after completing a fix, feature, or refactor
- Repairing a garbled PR description (
gh pr edit) - Updating the PR body after new commits
Prerequisites
ghCLI authenticated (gh auth status)- Working tree is clean or changes are committed
- Current branch is not
main(never create a new branch unless the current branch ismain— see AGENTS.md)
Procedure
Step 1 — Gather Context
Before writing the PR body, collect:
git log main..HEAD --oneline— commits included in the PRgit diff main --stat— files changed- Relevant plans or issues referenced by the branch name or commit messages
- Check for an existing PR:
gh pr list --head <branch>
Step 2 — Choose a Title
Format: <type>(<scope>): <short imperative summary> (conventional commits)
| Type | When |
|---|---|
feat | New user-visible capability |
fix | Bug fix |
perf | Performance improvement |
refactor | Internal restructure, no behaviour change |
test | Tests only |
docs | Documentation only |
chore | Build / CI / tooling |
Keep the title under 72 characters.
Step 3 — Write the PR Description
Structure the body using this template:
## Summary
<!-- 2-4 sentences: what changed and why -->
## Changes
<!-- Bullet list of the most important changes -->
- …
## Testing
<!-- How the change was verified -->
- `just test-unit` — passes
- `just test-integration` — passes
- `just test-e2e` — passes (include relevant test names if targeted)
## Notes
<!-- Optional: migration steps, rollback plan, known limitations, follow-up issues -->Show full SKILL.md (209 more words)Show less
Step 4 — Write Description Using create_file Tool
CRITICAL: Use the create_file tool — never echo or a shell heredoc.
Delete any stale file at the target path first:
bash rm -f /tmp/pr_<TICKETNAME>.mdUse
create_fileto write the body to/tmp/pr_<TICKETNAME>.md. The file is written in UTF-8 and read directly bygh --body-file, so Unicode characters (math symbols, em-dashes, arrows) are safe.Verify the file is clean before using it:
bash python3 -c " with open('/tmp/pr_<TICKETNAME>.md') as f: body = f.read() print('lines:', body.count(chr(10))) print('ok:', '####' not in body) print(body[:120]) "
Step 5 — Create or Update the PR
New PR:
gh pr create \
--title "<type>(<scope>): <summary>" \
--body-file /tmp/pr_<TICKETNAME>.md \
--base mainFix garbled description on existing PR:
gh pr edit <number> --body-file /tmp/pr_<TICKETNAME>.mdStep 6 — Verify the Live PR Body
gh pr view <number> --json body --jq '.body' | head -20Confirm the first heading and a Unicode character (if any) render correctly. If the body is garbled, re-run Step 3–5.
Branch Rules
- Never create a new git branch unless the current branch is
main. - Branch names follow
<type>/<short-slug>, e.g.fix/scheduler-race,feat/window-function-diff.
Checklist Before Opening the PR
-
just fmt && just lintpasses with zero warnings - Relevant test tier passes (
just test-unit/just test-integration/just test-e2e) - No
unwrap()/panic!()in non-test code paths - All
unsafeblocks have// SAFETY:comments - PR title follows conventional commit format
- PR body written via
create_filetool (not heredoc / echo) - Live PR body verified with
gh pr view
© trickle-labs, 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 .github/skills/create-pull-request of trickle-labs/pg-trickle.
Open the folder on GitHubat commit 101c5d3
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Create Pull Request this skilltrickle-labs/pg-trickle | 147 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
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.
PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
WooCommerce Code Review
woocommerce/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
More from trickle-labs/pg-trickle
Enrich Release Roadmap
trickle-labs/pg-trickle
Enrich a pgtrickle release roadmap with prioritised items across six quality pillars: correctness, stability, performance, scalability, ease-of-use, and test coverage.
Implement Roadmap Version
trickle-labs/pg-trickle
Implement all items for a specific version in the pgtrickle roadmap.
Improve Documentation
trickle-labs/pg-trickle
Reviews and improves the pgtrickle documentation in docs/. An agent skill from trickle-labs/pg-trickle.
Related
Categories
Questions about Create Pull Request
What does Create Pull Request do?
Create or update a pull request for pgtrickle. An agent skill from trickle-labs/pg-trickle. Create Pull Request is an agent skill from trickle-labs/pg-trickle. Create or update a pull request for pgtrickle.
When should I use Create Pull Request?
Create Pull Request fits situations like: : opening a new PR; fixing a garbled PR description; updating an existing PR body; preparing a PR after finishing a feature.
How do I install Create Pull Request in Claude Code?
Run `npx skills add trickle-labs/pg-trickle --skill create-pull-request -a claude-code`. Or copy the skill folder (.github/skills/create-pull-request in trickle-labs/pg-trickle) 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 trickle-labs/pg-trickle --skill create-pull-request -a codex`. Or copy the skill folder (.github/skills/create-pull-request in trickle-labs/pg-trickle) 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 trickle-labs/pg-trickle --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 (gh, just, git and python3). Our summary lists: Python 3.
Does Create Pull Request access the network?
SKILL.md contains no URLs. Its commands use gh and git, 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 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 Pull Request use?
About 1.1k tokens (SKILL.md is roughly 4.2k 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: Finishing a Development Branch (obra/superpowers, 296k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k 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?
trickle-labs (a GitHub organization) maintains it in trickle-labs/pg-trickle, which has 147 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.
Source: trickle-labs/pg-trickle on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.