02-pull-request — Claude Code skill for draft requests
02-pull-request collects changes from the current branch and opens a draft pull or merge request. Use it when you want a review request prepared without publishing it as ready.
MIT ★ 571 updated 2026-10-29
/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-vcs@aidd-frameworkWhat 02-pull-request does
The skill finds the base branch from the project’s conventions or falls back to the repository’s default branch, then gathers commits against it. It writes a title and description using the project’s request template, creates a draft, applies the matching label, and returns the request URL.
Before each action, it reads the corresponding file in actions/. It follows aidd_docs/memory/vcs.md and the repository’s own template; when there is no repository template, it uses assets/pull_request.md. It does not assume the base is main. The request stays in draft until the user promotes it. This skill does not commit, push, or create branches.
What it helps with
- gather commits from the current branch against its base
- write a request title and description from a template
- open a draft pull or merge request
- apply the branch-prefix label and return the request URL
Example prompts for the agent
- Prepare a draft pull request for the current branch.
- Compare this branch with
releaseand open a draft request titled “Update export”. - Create a merge request using the repository template, without pushing changes.
How to install 02-pull-request
1Plugin marketplace
/plugin marketplace add ai-driven-dev/framework/plugin install aidd-vcs@aidd-frameworkThis installs the whole aidd-vcs plugin with all its skills
2Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 02-pull-request -a claude-code3Manually: put the files in place
~/.claude/skills/02-pull-request/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/02-pull-request/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 02-pull-request -a codex2Manually: put the files in place
.agents/skills/02-pull-request/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 02-pull-request -a cursor2Manually: put the files in place
.cursor/skills/02-pull-request/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ai-driven-dev/framework plugins/aidd-vcs/skills/02-pull-request2Manually: put the files in place
.github/skills/02-pull-request/SKILL.md1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 02-pull-request -a gemini-cli2Platform CLI
gemini skills install https://github.com/ai-driven-dev/framework --path plugins/aidd-vcs/skills/02-pull-requestManually: put the files in place
.devin/skills/02-pull-request/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 02-pull-request -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 02-pull-request
How do I install 02-pull-request in Claude Code?
Add the marketplace with /plugin marketplace add ai-driven-dev/framework, then install the plugin with /plugin install aidd-vcs@aidd-framework.
What does 02-pull-request do?
It gathers commits from the base branch, drafts the request using a template, and opens a pull or merge request in draft state. It then applies a matching label and returns the URL.
How does the skill choose the base branch?
It first follows the project convention in aidd_docs/memory/vcs.md. If that guidance is absent, it uses the repository’s default branch rather than assuming main.
Source text
SKILL.md · MIT
--- name: 02-pull-request description: Create a draft pull or merge request from the current branch, in whatever VCS tool the project uses. Use when the user wants to open a pull or merge request. Not for committing, pushing, or merging a branch. argument-hint: base | title --- # Pull Request Collect the change, draft the request, create it as a draft. `01 → 02 → 03`. ## Actions | # | Action | Step | | --- | --------- | ----------------------------------------------------------- | | 01 | `collect` | Resolve the base and gather the commits since it | | 02 | `draft` | Write the title and body from the template | | 03 | `create` | Open the draft request, label it, return the URL | Before running an action, read its file in `actions/`, not only the table or assets. ## Transversal rules - Follow the project's request practices in `aidd_docs/memory/vcs.md` and the repo's own request template when set, else the bundled `assets/pull_request.md`. - Resolve the base from the branch's prefix per the project's convention (`vcs.md`), else the repo's default branch. Never assume `main`. - The request is always a draft; the user promotes it. - Apply only the triage label the branch prefix maps to, when it exists. Labels never change the base. - Read the VCS tool from project memory, else infer it from the remote URL. - Never commit, push, or branch here. ## Assets - `assets/pull_request.md`: Request body template. - `assets/branch.md`: Branch-naming convention, the fallback when project memory sets none.
© AI-Driven Dev · MIT · ai-driven-dev/framework