Create pr

Skill Guild-Agents/guild/.claude/skills/create-pr

Create a pull request from the current branch with structured summaryFrom its SKILL.md

Install

npx -y skills add Guild-Agents/guild --skill create-pr

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.2 KB, as published. Nobody here has run it

Create PR

Creates a pull request from the current feature branch with a structured summary, test results, and change description. Closes the pipeline loop: init -> build-feature -> create-pr.

When to use

After completing a feature with /build-feature
When you have changes on a feature branch ready for review
To create a well-structured PR without manual formatting

Usage

/create-pr

Process

Step 1 -- Verify branch state

Confirm you are NOT on main or develop -- refuse to create PR from default branches
Run git status to check for uncommitted changes -- if any, warn the user and ask whether to commit first
Run git log main..HEAD --oneline to get the list of commits that will be in the PR
If there are no commits ahead of main, report that there is nothing to PR

Step 2 -- Gather context

Collect the information needed for the PR description:

Commits: git log main..HEAD --oneline -- list of all commits on this branch
Diff summary: git diff main..HEAD --stat -- files changed with line counts
Test results: Run project tests (e.g., npm test) and capture pass/fail
Lint results: Run project lint (e.g., npm run lint) and capture pass/fail
Branch name: Extract feature name from the branch (e.g., feature/dark-mode -> dark-mode)

If tests or lint fail, warn the user but allow them to proceed (some PRs are draft/WIP).

Step 3 -- Generate PR description

Build a structured PR description:

## Summary
[2-4 bullet points describing what this PR does, derived from commit messages]

## Changes
[File-level summary from git diff --stat]

## Test plan
- [x] Tests: [pass/fail] ([count] tests)
- [x] Lint: [pass/fail]
- [ ] [Any manual verification steps if applicable]

Step 4 -- Create the PR

Push the branch to origin: git push -u origin [branch-name]
Create the PR using gh pr create:
- Title: derived from branch name or first commit message (max 70 chars)
- Body: the generated description from Step 3
- Base: main (or the project's default branch)
Report the PR URL to the user

Step 5 -- Post-creation

Display the PR URL
Suggest next steps:
- "Request review from a teammate"
- "Run /code-review for an AI code review"
- "Merge when ready with gh pr merge [number]"

Example Session

User: /create-pr

Checking branch state...
Branch: feature/dark-mode (4 commits ahead of main)
Tests: 82 passed, 0 failed
Lint: 0 errors

Creating PR...
PR #42: "feat: add dark mode toggle to settings"
https://github.com/org/repo/pull/42

Next steps:
- Request review from a teammate
- Run /code-review for AI code review
- Merge when ready

Notes

The PR title should be concise (under 70 characters) and follow conventional commits format when the project uses it
If the branch has wip: commits from build-feature checkpoints, consider squashing them before creating the PR
This skill does NOT merge the PR -- that is a manual step or a separate command