Streamlines opening and validating pull requests using templates and automated checks.
Install
mkdir -p .claude/skills/pr-zacharyfmarion && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18087" && unzip -o skill.zip -d .claude/skills/pr-zacharyfmarion && rm skill.zipInstalls to .claude/skills/pr-zacharyfmarion
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when the user wants to open a pull request or finish a branch handoff. Read the PR template, inspect changes vs main, run the release skill first if the branch name looks like a version, validate the branch with the shared repo checks, open a draft PR targeting main, and return the preview deployment URL when one applies.Key capabilities
- →Read `.github/PULL_REQUEST_TEMPLATE.md` to understand required sections
- →Inspect changes on the current branch versus `main`
- →Run validation scripts with specified scopes
- →Draft a PR title and body following the template
- →Create or update a draft PR against `main`
- →Return the full PR URL and preview URL
How it works
The skill automates the pull request creation process by reading templates, inspecting changes, running validations, and interacting with `gh pr create`.
Inputs & outputs
When to use pr
- →Open a pull request
- →Validate branch changes
- →Populate PR templates
- →Finish branch handoff
About this skill
Open Pull Request
- Read
.github/PULL_REQUEST_TEMPLATE.mdand understand its required sections. - Inspect what has changed on this branch vs
main. If there are unrelated changes, stop and ask the user what to do. - If the branch name looks like a release branch or versioned release workflow, run the release skill first before continuing.
- Choose the right validation scopes for the changed files and run them through
scripts/validate-changes.sh. - Prefer
bash scripts/validate-changes.sh --scope baselinefor normal TS or workflow changes. Add scopes when needed:--scope formatterfor formatter behavior changes--scope rustforapps/ui/src-taurior other desktop-only changes--scope e2e-webfor materially changed user-facing web flows
- If formatting fixes are still needed before validation, run
pnpm formatintentionally first, then rerun the validation helper in check mode. Do not rely on the helper to mutate files unless you explicitly choose--fix. - Draft a PR title and body that follow the template exactly, filling each section from the actual branch changes, validations run, validations skipped, and tests added.
- Open or update a draft PR against
main:- Create with
gh pr create --draft --base mainwhen no PR exists for the branch. - Update the existing PR body when one already exists.
- Create with
- After the PR exists, wait for the
Deploy PR Previewworkflow when the change is web-relevant. - Return:
- the full PR URL
- the preview URL when one applies
- any explicit follow-up if the preview deploy or sticky comment failed
Preview Expectations
- Web-relevant PRs should publish to
https://pr-<number>.openscad-studio.pages.dev - Docs-only and desktop-only PRs may skip preview deployment
- If Cloudflare deploy succeeds but the sticky comment fails, report that separately instead of pretending the preview is unavailable
When not to use it
- →When the branch name looks like a release branch or versioned release workflow
- →When there are unrelated changes on the branch without user instruction
Limitations
- →Requires user intervention for unrelated changes on the branch
- →Requires `gh` CLI for PR creation
- →Does not automatically handle release branch workflows
How it compares
This skill provides a structured and automated workflow for creating pull requests, ensuring adherence to templates and validation checks, unlike manual PR creation.
Compared to similar skills
pr side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pr (this skill) | 0 | 4mo | No flags | Intermediate |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| dependency-upgrade | 26 | 4mo | Review | Intermediate |
| git-commits | 21 | 3mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
git-commits
bonny
Create well-structured git commits in logical chunks following best practices
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
github-multi-repo
ruvnet
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration
git-workflow-enforcer
CrazyDubya
Ensures commits follow conventional commits, branch naming conventions, and PR templates. Use when creating commits, branches, or PRs, or when user mentions git workflow.