Create a pull request from dev to main with proper formatting and draft release
npx skills add https://github.com/glowingkitty/OpenMates --skill create-pr이 명령을 Claude Code에 복사하여 붙여넣어 스킬을 설치하세요
Create OpenMates marketing videos from script notes using the external Remotion workspace, product-accurate UI rebuilds, optional Playwright recordings, renders, and review uploads.
Integrate a new external API provider (research, wrapper, test script, docs)
Scaffold a new skill in an existing app (BaseSkill, schemas, app.yml, i18n)
Scaffold and register a new embed type (components, theme, icons, i18n, renderer)
Create a new hardcoded example chat from a shared chat URL with encryption key
Run a structured 5-round Q&A to fully understand a bug or feature request before writing any code. Outputs a Task Brief with user flow, acceptance criteria, scope, edge cases, affected areas, and open questions. Use at the start of any non-trivial session.
| name | create-pr |
| description | Create a pull request from dev to main with proper formatting and draft release |
| user-invocable | true |
| disable-model-invocation | false |
| argument-hint | [title] |
!git fetch origin main dev 2>/dev/null && echo "=== Commit count (main-ahead : dev-ahead) ===" && git rev-list --left-right --count origin/main...origin/dev && echo "" && echo "=== Commits on dev not in main ===" && git log --oneline origin/main..origin/dev
!git diff --stat origin/main...origin/dev 2>/dev/null | tail -30
!gh release list --limit 3 2>/dev/null || echo "gh not available"
IMPORTANT: Only create a PR when the user explicitly asks.
ALWAYS use remote refs (origin/main, origin/dev) — never local refs. Local refs can be stale and produce wildly incorrect commit counts.
git fetch origin main dev
git rev-list --left-right --count origin/main...origin/dev
git log --oneline origin/main..origin/dev
The output above already did this. Confirm the commit count makes sense before proceeding. If something looks off, tell the user and stop.
Read the full commit messages (not just one-liners):
git log origin/main..origin/dev --format="%h %s%n%b"
Group commits into:
feat:) — new user-facing functionalityfix:) — resolved issuesrefactor:, perf:, improve:) — internal improvementsdocs:, chore:, build:, ci:, test:) — maintenanceWrite a human-readable PR description — not a commit dump. Structure:
## Summary
<2-4 sentence overview of what this PR does and why>
## Features
- <grouped by feature area>
## Bug Fixes
- <grouped by fix area>
## Improvements
- <grouped by improvement area>
## Other Changes
- <docs, chore, config items>
Only include sections that have content. Write for a developer audience — specific and clear.
gh pr create --base main --head dev --title "<short descriptive title>" --body "$(cat <<'EOF'
<PR description>
EOF
)"
Present the PR URL to the user.
After PR creation, ask the user if they want a draft release prepared. If yes, use the /create-release skill. Tell the user:
main