SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Devops / AGENT SKILL
pr
0
Opens pull requests with conventional titles, structured descriptions, and pre-flight checks.
Open a pull request with conventional title, structured description, and pre-flight checks.
Understand the trade-offs.
SKILL QUALITY
Not yet assessed
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
The full skill.
Original instructions from the publisher’s SKILL.md
# 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 name
- `git log main..HEAD --oneline` — commits on this branch
- `git 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:
```markdown
## 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.