Write a PR description using conversation context and open PR creation in browser.
Scanned 8/31/2026
Install to Claude Code
Skills Directorynpx -y skills add okm321/dotfiles --skill open-pr --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Open Pr?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/okm321-open-pr)More formats (shields.io, HTML) on the badges page.
---
name: open-pr
description: Write a PR description using conversation context and open PR creation in browser.
disable-model-invocation: true
allowed-tools: Read, Bash, Glob, Grep
---
<!-- This is a starting point. Customize the template and guidelines to match your team's PR conventions. -->
## Gather context
1. Get the base branch (usually `main` or `master`)
2. Get the diff: `git diff <base>...HEAD`
3. Get commit messages: `git log <base>...HEAD --format="%s"`
4. Read changed files to understand the broader context
## Commit uncommitted changes
1. Run `git status` to check for uncommitted changes
2. If changes exist, commit them before proceeding
## Write PR description
Use this template:
```markdown
## Summary
[1-2 sentences: what this PR does and why]
## Changes
- [Key change 1]
- [Key change 2]
- [Key change 3]
## Testing
[How you verified it works]
```
Guidelines:
- Lead with a concise summary of what the PR does
- Explain the "why" before the "how"
- Use the conversation context to inform the description
- Include before/after comparisons for UI or performance changes
- Be direct and to the point
## Create the PR
1. Write a short PR title (max 72 characters)
2. Ensure the branch is pushed:
```bash
git push -u origin HEAD
```
3. Open PR creation in browser (do NOT create directly):
```bash
gh pr create --web --title "<title>" --body "<body>"
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Discover the pull requests this Paperclip instance opened (never community contributions), report what each is for and how confident we are that it is merge-ready, and automatically drive the non-ready ones back to green with /prepare-paperclip-pr — without ever merging.
