Create valid PRs that meet all project quality requirements before submission.
Install
mkdir -p .claude/skills/pr-ashaychangwani && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13466" && unzip -o skill.zip -d .claude/skills/pr-ashaychangwani && rm skill.zipInstalls to .claude/skills/pr-ashaychangwani
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.
Open a pull request with conventional title, structured description, and pre-flight checks.Key capabilities
- →Run lint, typecheck, and test pre-flight checks
- →Gather Git context like current branch and commits
- →Determine PR title using conventional commit format
- →Write a structured PR description with summary and test plan
- →Create a pull request using `gh pr create`
How it works
The skill automates the pull request creation process by running pre-flight checks, gathering Git information, and structuring the PR title and description.
Inputs & outputs
When to use pr
- →Submitting feature PRs
- →Running CI checks before submission
- →Documenting changes and design decisions
About this skill
PR Skill
Open a pull request for the current branch with proper conventions.
Step 1 — Pre-flight checks
Run these in parallel and report results:
bun run lint
bun run typecheck
bun test
If any fail, show the errors and ask the user whether to proceed or fix first.
Step 2 — Gather context
Run these to understand the branch:
git branch --show-current— current branch namegit log main..HEAD --oneline— commits on this branchgit diff main..HEAD --stat— files changed
Step 3 — Determine PR title
The PR title must be a conventional commit format: <type>(<scope>): <description>
Pick type and scope the same way as the /commit skill, but based on the overall branch intent (not individual commits).
Step 4 — Write PR description
Use this structure:
## Summary
- Bullet 1: what changed and why
- Bullet 2: key design decisions
- Bullet 3: anything reviewers should pay attention to
## Test plan
- [ ] Tests pass locally
- [ ] Specific scenario tested
Step 5 — Check remote
Run git remote -v and git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null to check if the branch is pushed.
If not pushed, run git push -u origin <branch>.
Step 6 — Create PR
gh pr create --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"
Show the PR URL to the user when done.
When not to use it
- →The user does not want to enforce conventional commit format for PR titles
- →The user does not want to run automated pre-flight checks
Limitations
- →It relies on `bun` for lint, typecheck, and test commands
- →It enforces a specific conventional commit format for PR titles
- →It requires `gh` CLI for creating the pull request
How it compares
This workflow enforces conventions and automates checks, ensuring consistent and well-documented pull requests, 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 | 3mo | No flags | Intermediate |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| testing-workflow | 16 | 9mo | Review | Intermediate |
| finishing-a-development-branch | 4 | 3mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
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.
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
finishing-a-development-branch
obra
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
dev
atopile
LLM-focused workflow for working in this repo: compile Zig, run the orchestrated test runner, consume test-report.json/html artifacts, and discover/debug ConfigFlags.
positron-pr-helper
posit-dev
Generates well-structured PR bodies with dynamically fetched e2e test tags
test-script
abhinav
Use when writing or modifying .txt test scripts in testdata/script/ for git-spice - covers txtar format, end-to-end testing, ShamHub forge simulation, interactive prompts, and golden file comparisons for branch operations and stack workflows.