How do I install the Create Pr skill?

Run npx skillmds@latest add dojoengine/create-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Create Pr skill do?

Create or update a PR from current branch to main and address feedback It is listed under Coding & Dev Tools on SkillMD.

Is Create Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Create Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Create Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Create Pr?

dojoengine (@dojoengine) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Create Pr by dojoengine — Agent Skill

Name: Create Pr
Author: dojoengine

File contents

The user likes the state of the code.

There are $git status --porcelain | wc -l | tr -d ' ' uncommitted changes. The current branch is $git branch --show-current. The target branch is origin/main.

$git rev-parse --abbrev-ref @{upstream} 2>/dev/null && echo "Upstream branch exists." || echo "There is no upstream branch yet."

Existing PR: $gh pr view --json number,title,url --jq '"#\(.number): \(.title) - \(.url)"' 2>/dev/null || echo "None"

The user requested a PR.

Follow these exact steps:

Phase 1: Review the code

Review test coverage
Check for silent failures
Verify code comments are accurate
Review any new types
General code review

Phase 2: Create/Update PR

Run git diff to review uncommitted changes
Commit them. Follow any instructions the user gave you about writing commit messages.
Push to origin.
Use git diff origin/main... to review the full PR diff
Check if a PR already exists for this branch:

If PR exists:
- Draft/update the description in a temp file (e.g. /tmp/pr-body.txt).
- Update the PR body using the non-deprecated script:
  - ./.agents/skills/create-pr/scripts/pr-body-update.sh --file /tmp/pr-body.txt
- Re-fetch the body with gh pr view --json body --jq .body to confirm it changed.
If no PR exists: Use gh pr create --base main to create a new PR. Keep the title under 80 characters and the description under five sentences.

The PR description should summarize ALL commits in the PR, not just the latest changes.

Phase 3: Completion

Report the PR URL to the user. Do not poll for CI status — the user monitors CI externally.
If the user reports CI failures or review feedback, address them:
- Fix issues, commit, and push
- For bot reviews, address clearly actionable comments (bug fixes, typos, simple improvements)
- Skip comments that require design decisions or user input
If the user asks to merge:
- Use gh pr merge --squash --delete-branch to squash-merge and delete the remote branch
- Check if we're in a git worktree: [ "$(git rev-parse --git-common-dir)" != "$(git rev-parse --git-dir)" ]
- If in a worktree: Ask if they want to clean up the worktree. If yes, run wt remove --yes --force.
- If not in a worktree: git checkout main && git pull

If any step fails in a way you cannot resolve, ask the user for help.

---name: create-prdescription: Create or update a PR from current branch to main and address feedback---The user likes the state of the code.There are $`git status --porcelain | wc -l | tr -d ' '` uncommitted changes.The current branch is $`git branch --show-current`.The target branch is origin/main.$`git rev-parse --abbrev-ref @{upstream} 2>/dev/null && echo "Upstream branch exists." || echo "There is no upstream branch yet."`**Existing PR:** $`gh pr view --json number,title,url --jq '"#\(.number): \(.title) - \(.url)"' 2>/dev/null || echo "None"`The user requested a PR.Follow these exact steps:## Phase 1: Review the code1. Review test coverage2. Check for silent failures3. Verify code comments are accurate4. Review any new types5. General code review## Phase 2: Create/Update PR6. Run `git diff` to review uncommitted changes7. Commit them. Follow any instructions the user gave you about writing commit messages.8. Push to origin.9. Use `git diff origin/main...` to review the full PR diff10. Check if a PR already exists for this branch: - **If PR exists**: - Draft/update the description in a temp file (e.g. `/tmp/pr-body.txt`). - Update the PR body using the non-deprecated script: - `./.agents/skills/create-pr/scripts/pr-body-update.sh --file /tmp/pr-body.txt` - Re-fetch the body with `gh pr view --json body --jq .body` to confirm it changed. - **If no PR exists**: Use `gh pr create --base main` to create a new PR. Keep the title under 80 characters and the description under five sentences.The PR description should summarize ALL commits in the PR, not just the latest changes.## Phase 3: Completion11. Report the PR URL to the user. Do not poll for CI status — the user monitors CI externally.12. If the user reports CI failures or review feedback, address them: - Fix issues, commit, and push - For bot reviews, address clearly actionable comments (bug fixes, typos, simple improvements) - Skip comments that require design decisions or user input13. If the user asks to merge: - Use `gh pr merge --squash --delete-branch` to squash-merge and delete the remote branch - Check if we're in a git worktree: `[ "$(git rev-parse --git-common-dir)" != "$(git rev-parse --git-dir)" ]` - **If in a worktree**: Ask if they want to clean up the worktree. If yes, run `wt remove --yes --force`. - **If not in a worktree**: `git checkout main && git pull`If any step fails in a way you cannot resolve, ask the user for help.

Frequently asked questions

Create Pr