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.
Draft pull requests with structured descriptions using gh CLI
$ npx skills add jellydn/my-ai-tools --skill draft-pull-request -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jellydn/my-ai-tools draft-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/jellydn/my-ai-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/draft-pull-request .claude/skills/draft-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 "draft-pull-request" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/draft-pull-request into .claude/skills/draft-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-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/jellydn/my-ai-tools/tree/main/skills/draft-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 jellydn/my-ai-tools --skill draft-pull-request -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jellydn/my-ai-tools draft-pull-request --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/draft-pull-request .agents/skills/draft-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 "draft-pull-request" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/draft-pull-request into .agents/skills/draft-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-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 jellydn/my-ai-tools --skill draft-pull-request -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jellydn/my-ai-tools draft-pull-request --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/draft-pull-request .cursor/skills/draft-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 "draft-pull-request" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/draft-pull-request into .cursor/skills/draft-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-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/jellydn/my-ai-tools.git --path skills/draft-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 jellydn/my-ai-tools --skill draft-pull-request -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jellydn/my-ai-tools draft-pull-request --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/draft-pull-request .gemini/skills/draft-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 "draft-pull-request" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/draft-pull-request into .gemini/skills/draft-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-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 jellydn/my-ai-tools draft-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 jellydn/my-ai-tools --skill draft-pull-request -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/draft-pull-request .github/skills/draft-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 "draft-pull-request" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/draft-pull-request into .github/skills/draft-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-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 jellydn/my-ai-tools --skill draft-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 jellydn/my-ai-tools draft-pull-request --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jellydn/my-ai-tools.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/draft-pull-request .opencode/skills/draft-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 "draft-pull-request" agent skill from https://github.com/jellydn/my-ai-tools/tree/main/skills/draft-pull-request into .opencode/skills/draft-pull-request/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "draft-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.
draft-pull-requestDraft pull requests with structured descriptions using gh CLI
Draft Pull Request is an agent skill from jellydn/my-ai-tools. Draft pull requests with structured descriptions using gh CLI
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/change-outline.md` and `references/pr-body-template.md`). Compatibility notes: cline, claude, opencode, amp, codex, gemini, cursor, pi
It sits in Development, covering Pull requests. The repository describes itself as: Comprehensive configuration management for AI coding tools - Replicate my complete setup for Claude Code, OpenCode, Amp, Li, Codex and Claude Code Switch with custom… The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 163951e. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
ghgitFrom the folder's file list and the shell code blocks in SKILL.md.
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.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
cline, claude, opencode, amp, codex, gemini, cursor, pi
From compatibility in the SKILL.md frontmatter.
Draft Pull Request loads about 1.4k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 20 tokens; SKILL.md has 466 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.
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.
The full file from jellydn/my-ai-tools at commit 163951e, republished under its MIT licence (© jellydn). 466 words, ~1,441 tokens.
.claude/skills/draft-pull-request/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Create a draft pull request, or update the current branch's PR, with a What / Why / How description. The description must let a reviewer understand why the change exists and the shape of the implementation without reading every line of the diff.
/draft-pull-request [title]$ARGUMENTS, use it as the PR title.| File | Read when |
|---|---|
$SKILL_PATH/references/pr-body-template.md | Always, before you write the PR body |
$SKILL_PATH/references/change-outline.md | The How section needs a file tree, call tree, or shape |
BASE_BRANCH=$(gh repo view --json defaultBranchRef -q '.defaultBranchRef.name')
git branch --show-current
git status --short --branch
# Reuse an existing PR for this branch instead of opening a duplicate
gh pr view --json number,url,title,state,isDraft,baseRefName,body 2>/dev/nullBASE_BRANCH to its baseRefName, which may differ from the default branch, and update
its body in step 4. Do not create a second PR or change its draft state.commit-atomic when it is available). Leave unrelated or
unfamiliar changes uncommitted and mention them in the final report.git fetch origin "$BASE_BRANCH" --quiet
git log "origin/$BASE_BRANCH"..HEAD --oneline
git diff "origin/$BASE_BRANCH"...HEAD --stat
git diff "origin/$BASE_BRANCH"...HEADgh pr diff <number> and gh pr view <number> --json commits,files.
This stays correct when the branch lives in a fork and origin is not the base repository.$SKILL_PATH/references/pr-body-template.md and follow its rules..github/pull_request_template.md, .github/PULL_REQUEST_TEMPLATE/,
or docs/pull_request_template.md), keep its headings and checklists, and put the What / Why / How content into
the matching sections.$SKILL_PATH/references/change-outline.md and add
one to three small views to How.BODY_FILE=$(mktemp "${TMPDIR:-/tmp}/pr-body.XXXXXX")# Never force-push.
git push -u origin HEAD
# New PR
gh pr create --draft --base "$BASE_BRANCH" --title "<PR title>" --body-file "$BODY_FILE"
# Existing PR from step 1
gh pr edit <number> --body-file "$BODY_FILE"Use --body-file instead of --body so that Markdown, backticks, and code fences survive shell quoting.
gh pr edit --body-file replaces the whole body. Before you edit an existing PR, carry over from its current body
anything the diff cannot tell you: links, reviewer notes, and checklist items that someone ticked and that still apply.
gh pr view --json url,title,isDraft -q '"\(.url) draft=\(.isDraft) \(.title)"'
rm -f "$BODY_FILE"Reply with:
- PR: [#<number> <title>](<url>) (<draft or ready for review, from isDraft>)
- Summary: <2-3 sentences: what the PR does and the key decision>
- Validation: <commands run and their results, or "not run">
- Left out: <uncommitted or unrelated changes, or "none">feat(auth): add JWT refresh token support).references/pr-body-template.md; do not restate them here.Closes #142
## What
Add a refresh-token endpoint and automatic token renewal in the API client.
## Why
Users are logged out when the 1-hour access token expires, which interrupts long sessions.
## How
- `POST /auth/refresh` validates the HttpOnly refresh cookie and issues a new access token.
- The API client retries a `401` response once, after a refresh, before it shows an error.
```diff
request(url)
send with access token
+ if status is 401 and not retried
+ refreshToken()
+ retry once
return response
```
## Reviewer notes
- Refresh tokens rotate on each use; a reused token revokes the whole session.
## Validation
- `bun test src/auth` — 24 passed
- Manual: session stays signed in after the access token expires© jellydn, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (references) in skills/draft-pull-request of jellydn/my-ai-tools.
Open the folder on GitHubat commit 163951e
Draft 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 |
|---|---|---|---|---|---|---|
| Draft Pull Request this skilljellydn/my-ai-tools | 123 | — | ~1.4k | Automated safety check: Pass | MIT | |
| 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 | 85k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT |
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.
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
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.
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.
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/woocommerce
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
jellydn/my-ai-tools
A skill your agent uses when monitoring an open GitHub PR for CI failures, review feedback, mergeability, and safe retries or fixes.
jellydn/my-ai-tools
Posts a concise visual outline as a GitHub pull request comment.
jellydn/my-ai-tools
Manage project knowledge with qmd — captures learnings, decisions, and conventions
jellydn/my-ai-tools
Generate Product Requirements Documents from feature ideas — plans specs and requirements
jellydn/my-ai-tools
Build an interactive report or experiment when the user asks to explore model capabilities.
jellydn/my-ai-tools
Fix PR review comments by implementing requested changes. An agent skill from jellydn/my-ai-tools.
Categories
Draft pull requests with structured descriptions using gh CLI. Draft Pull Request is an agent skill from jellydn/my-ai-tools.
Draft Pull Request fits situations like: tasks that involve Pull requests.
Run `npx skills add jellydn/my-ai-tools --skill draft-pull-request -a claude-code`. Or copy the skill folder (skills/draft-pull-request in jellydn/my-ai-tools) into .claude/skills/draft-pull-request in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jellydn/my-ai-tools --skill draft-pull-request -a codex`. Or copy the skill folder (skills/draft-pull-request in jellydn/my-ai-tools) into .agents/skills/draft-pull-request in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jellydn/my-ai-tools --skill draft-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/draft-pull-request, .gemini/skills/draft-pull-request, .github/skills/draft-pull-request and .opencode/skills/draft-pull-request in your project.
Going by SKILL.md and its folder, Draft Pull Request needs the command-line tools its instructions call (gh and git). Compatibility (from SKILL.md): cline, claude, opencode, amp, codex, gemini, cursor, pi.
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.
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.
Draft Pull Request is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Draft 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, 85k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jellydn (a GitHub user) maintains it in jellydn/my-ai-tools, which has 123 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 7, 2026.
Source: jellydn/my-ai-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.