Automates the PR lifecycle with build verification and Git flows.
Install
mkdir -p .claude/skills/pr-boundless-xyz && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13190" && unzip -o skill.zip -d .claude/skills/pr-boundless-xyz && rm skill.zipInstalls to .claude/skills/pr-boundless-xyz
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.
Create or update a pull request for the current git changes. Use when the user wants a PR, commit/push for review, or gh pr create flow.Key capabilities
- →Inspect staged, unstaged, and untracked changes
- →Run `forge build` before `cargo check`
- →Run `just check-main` or `just check` based on changes
- →Write a clear commit message
- →Commit and push to the current branch
- →Open a GitHub PR creation page with title and description
How it works
The skill inspects git changes, runs build and check commands, then commits and pushes the changes. It then opens a GitHub PR creation page with a generated title and description.
Inputs & outputs
When to use pr
- →Automate PR submission
- →Verify Rust builds before PR
- →Update existing PRs
About this skill
Create or update pull request
Instructions
- Look at the staged, unstaged, and untracked changes with
git diff - Run
forge buildbefore the cargo check step. Rust crates that bind to Solidity contracts (e.g.boundless-test-utilsreferencingVeZKC) fail to compile until the contract artifacts exist. Skipping this produces misleading "undeclared type" errors that look like real bugs. - If no changes to examples/ directory, run
just check-main. Else runjust check.- If fails, propose fixes and wait for approval
- If there are untracked files, do not add them to the commit, but warn the user
- Write a clear commit message based on what changed (use commit message style below)
- Commit and push to the current branch
- Check if an existing PR exists. Ignore warnings about GraphQL: Projects (classic) being deprecated.
- If not, do not submit the PR, but use
gh pr create --web --title <title> --body <body>to open the create PR page with title/description (use PR Title/Description Guidelines below) - Else update the description with the new changes.
- If not, do not submit the PR, but use
- Do not submit the PR. Just return the PR creation page URL when done
Commit message style
- Simple, one sentence
- Do not include a
--trailerwhen doing git commit
PR Title/Description Guidelines
- Do not include made with Cursor or similar line
- Title/description should describe all changes across all commits, i.e. all the changes vs origin/main
Writing Style — Sound Human, Not AI-Generated
Write like a developer talking to their team, not like a language model generating documentation.
Structure and tone
- Be direct and concise — skip filler phrases like "This PR introduces...", "This change aims to...", "In order to facilitate..."
- Lead with what changed and why — not with a preamble about the problem space
- Keep bullet points short — 1-2 sentences max per bullet. No sub-bullets unless truly needed
- Skip the obvious — don't describe what's clear from the diff (e.g. "Updated imports" or "Added new file X.rs")
- No sign-off or summary section — just end when you're done
- Match the tone of a brief Slack message, not a design doc
Banned words and phrases (AI vocabulary tells)
These words appear at dramatically higher rates in AI-generated text and are dead giveaways. Never use them:
- Puffery: "pivotal", "crucial role", "cornerstone", "testament to", "represents a significant", "broader landscape"
- Fancy verbs: "leverage" (say "use"), "facilitate" (say "help"), "showcase" (say "show"), "navigate" (say "handle"), "underscore", "foster", "bolster", "spearhead", "harness", "streamline", "delve"
- Filler adjectives: "robust", "comprehensive", "multifaceted", "nuanced", "holistic", "intricate", "seamless"
- Hedging: "It's worth noting...", "It should be noted...", "It's important to mention...", "One cannot overstate..."
- False depth: "Despite [positive], [subject] faces challenges...", "While [X], it's important to note [Y]..."
Plain language replacements
- "addresses" → "fixes"
- "introduces" → "adds"
- "has been updated to" → "now does"
- "serves as a" → "is"
- "leverages" → "uses"
- "facilitates" → "helps" or "lets"
- "utilizing" → "using"
- "prior to" → "before"
Other AI tells to avoid
- Rule of three: don't always list exactly 3 things. Sometimes 2 is enough, sometimes 4 is better
- Synonym cycling: don't avoid repeating a word by using increasingly weird synonyms. Just say "the function" twice instead of "the function" then "the aforementioned utility"
- Formulaic structure: don't make every bullet follow the same grammatical pattern
- Excessive formatting: don't bold every other phrase or use bullets where prose works fine
Examples of AI-sounding vs human-sounding
❌ "This PR introduces a new indexing pipeline that aims to address the current limitations in our backfill process." ✅ "Adds a redrive lambda for re-processing failed indexer events."
❌ "The following changes have been implemented to improve the overall developer experience:" ✅ "Cleans up the CLI skill install flow — fewer prompts, better error messages."
❌ "This comprehensive update leverages a robust new architecture to facilitate seamless skill management." ✅ "Rewrites skill install to use symlinks instead of copying files."
Template
<1-2 sentence overview: what changed and why>
Changes
* <specific notable change>
* <specific notable change>
* ...
When not to use it
- →When the user wants to submit the PR directly
- →When the user wants to include untracked files in the commit
- →When the user wants to use AI-generated phrasing in PR descriptions
Prerequisites
Limitations
- →Does not submit the PR automatically
- →Does not add untracked files to the commit
- →Requires `forge build` and `just check` commands to be available
How it compares
This skill automates the pre-PR checks, commit message generation, and PR page setup, which typically involves several manual steps and adherence to specific style guidelines.
Compared to similar skills
pr side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pr (this skill) | 0 | 2mo | No flags | Intermediate |
| release-skills | 2 | 3mo | Review | Intermediate |
| icn-shipping | 0 | 6mo | No flags | Intermediate |
| ci-pr-helper | 0 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
release-skills
JimLiu
Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送".
icn-shipping
InterCooperative-Network
Prepare ICN branches for merge with required checks, doc/spec sync, clean git hygiene, and high-quality PR metadata.
ci-pr-helper
lance-format
Run local test/style checks and open GitHub PRs for lance-context. Use when asked to run CI-equivalent checks (uv pytest, ruff/pyright, cargo fmt/clippy/test) and then create a PR with a proper title/body.
release
k1-c
Check release readiness, preview changelog, and validate publishability. Use when preparing a release or checking version status.
pr
zmerlynn
Push a branch and open a PR with pre-flight checks
release-bump
mikeyobrien
Use when bumping ralph-orchestrator version for a new release, after fixes are committed and ready to publish