w-pr — Claude Code skill: create and install
The w-pr Claude Code skill creates or updates a pull request for the intended branch. It publishes the branch, writes the PR description, and checks the result.
MIT 647 installs ★ 1 updated 2026-10-02
npx skills add blockmatic-icebox/basilic-skills --skill w-pr -a claude-codeWhat w-pr does
w-pr publishes the intended branch and opens a pull request with the problem, resulting behavior, verification, and material limitations in its description. Task changes must be committed and validated first; the workflow can use w-commit and w-push for those steps. If it needs to create a branch, it fetches from origin before branching from origin/main.
When a PR already exists for the branch, the skill reuses it instead of opening a duplicate. It applies applicable labels and requested reviewers, then checks the title, base, and description before returning the PR link. Creating a PR does not authorize a merge or deployment.
What it helps with
- publish a branch and open its pull request
- write a PR description with verification evidence
- update an existing PR instead of duplicating it
- check the PR title, base, and description
Example prompts for the agent
- Publish this branch and open a pull request for it.
- Update the PR for this branch and check its description.
- Create a branch from
origin/mainand open a PR for it.
How to install w-pr
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-pr -a claude-code2Manually: put the files in place
~/.claude/skills/w-pr/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/w-pr/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-pr -a codex2Manually: put the files in place
.agents/skills/w-pr/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-pr -a cursor2Manually: put the files in place
.cursor/skills/w-pr/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install blockmatic-icebox/basilic-skills skills/workflow/w-pr2Manually: put the files in place
.github/skills/w-pr/SKILL.md1Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-pr -a gemini-cli2Platform CLI
gemini skills install https://github.com/blockmatic-icebox/basilic-skills --path skills/workflow/w-prManually: put the files in place
.devin/skills/w-pr/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add blockmatic-icebox/basilic-skills --skill w-pr -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 w-pr
How do I install w-pr in Claude Code?
Run npx skills add blockmatic-icebox/basilic-skills --skill w-pr -a claude-code. The skill file is at ~/.claude/skills/w-pr/SKILL.md.
What does w-pr do?
It publishes a branch and creates or updates its pull request. The skill writes the description, checks the resulting PR fields, and returns its link.
What happens if the branch already has a pull request?
w-pr reuses the existing PR rather than creating a duplicate.
Source text
SKILL.md · MIT
--- name: w-pr description: Create or update a reviewable pull request for the intended branch. disable-model-invocation: true --- Invocation requests publishing the intended branch and creating its PR. Follow [git publish](references/git-publish.md). The description is part of this playbook; do not use a separate generate-description step. 1. Ensure task-owned changes are committed and validated. Use [commit](../w-commit/SKILL.md) if needed. If this playbook must create a branch first, `git fetch origin` then `git switch -c <name> --no-track origin/main` — never skip fetch, never a stale local `main`. 2. Push the intended branch using [push](../w-push/SKILL.md). 3. Write a standalone description: problem, resulting behavior, verification evidence, and material limitations. Follow the repository template; never create an empty description. Use a conventional PR title when the repository requires it. 4. Reuse an existing PR for this branch rather than duplicating it. Use known applicable labels and requested reviewers; do not invent assignments. 5. With a CLI, write multiline text to a temporary file and pass the body-file option. Verify the resulting title, base, and description. Return the PR link. PR creation does not authorize merge or deployment.
© blockmatic-icebox · MIT · blockmatic-icebox/basilic-skills