PR Skill
SkillDev toolsOpen a pull request with conventional title, structured description, and pre-flight checks.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the PR Skill skill
What this skill tells your AI
The instructions your AI receives, as published by ashaychangwani/imprint in .agents/skills/pr/SKILL.md and read by ahel’s review.
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.
Signals
- GitHub stars
- 21
- Forks
- 1
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
pr-ashaychangwani- Source
- github.com/ashaychangwani/imprint