メニュー
Create a GitHub Pull Request to merge the current branch into main with a well-structured title and description using GitHub CLI. Use when the user asks to create a PR, open a pull request, submit a merge request, or send changes for review.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Turn app screenshots into a cinematic product video — a self-contained animated HTML showcase and an exported MP4. Use when the user has app screenshots (or the raw captures from deploy-ss) and wants a "product video", "promo video", "sizzle reel", "app trailer", "launch video", or a shareable motion showcase / App Store preview. Companion to deploy-ss (which makes the static store screenshots).
Generate App Store and Play Store deployment assets — iPhone screenshots, iPad screenshots, and a Play Store feature graphic — from raw app UI screenshots. Use this skill whenever the user has app screenshots and wants to publish to the App Store or Google Play, mentions "store screenshots", "marketing screenshots", "feature graphic", "app store assets", "App Store Connect", "Play Console", "Google Play listing", or asks how to prepare their app's listing for submission. Trigger this even when the user just uploads phone screenshots and says something vague like "make these look good for the store" or "I'm submitting my app, help me with the visuals" — those are still this skill.
Stage, commit, and push uncommitted code with a well-structured conventional commit message. Use when the user asks to push code, commit and push, save changes to remote, or sync local changes with GitHub.
Generate App Store and Play Store deployment assets — iPhone screenshots, iPad screenshots, and a Play Store feature graphic — from raw app UI screenshots. Use this skill whenever the user has app screenshots and wants to publish to the App Store or Google Play, mentions "store screenshots", "marketing screenshots", "feature graphic", "app store assets", "App Store Connect", "Play Console", "Google Play listing", or asks how to prepare their app's listing for submission. Trigger this even when the user just uploads phone screenshots and says something vague like "make these look good for the store" or "I'm submitting my app, help me with the visuals" — those are still this skill.
Merge an approved GitHub Pull Request after validating CI checks, review status, and mergeability. Use when the user asks to merge a PR, complete a pull request, or land a branch.
Run the full push, create PR, review pipeline in sequence: stage/commit/push (push-code), create a PR into main (create-pr), then approve or request changes on that PR (review-pr). Use when the user says pcr, push commit review, push and create pr and review, or wants one workflow from local changes to an opened and reviewed pull request.
| name | create-pr |
| description | Create a GitHub Pull Request to merge the current branch into main with a well-structured title and description using GitHub CLI. Use when the user asks to create a PR, open a pull request, submit a merge request, or send changes for review. |
Create a GitHub Pull Request from the current feature branch into main.
gh --version # GitHub CLI installed
gh auth status # Authenticated
git status # All changes committed and pushed
CURRENT_BRANCH=$(git branch --show-current)
If $CURRENT_BRANCH is main, master, dev, develop, or any protected branch:
git log main..HEAD --oneline # Commits since branching
git diff main...HEAD --name-only # Changed files
git diff main...HEAD --stat # Change summary
Format: [<TYPE>] <Brief description>
Examples:
[FEATURE] Add Binance WebSocket integration for real-time crypto prices[FIX] Resolve memory leak in RSS feed parser[REFACTOR] Restructure settings screen with improved UXUse this template:
## Description
[Clear explanation of what this PR does and why]
## Changes Made
- [Bullet point list of all changes]
- [Include file/module names]
- [Mention new dependencies if any]
## Type of Change
- [ ] New feature
- [ ] Bug fix
- [ ] Refactoring
- [ ] Documentation update
- [ ] Performance improvement
## Testing Done
- [ ] Unit tests added/updated
- [ ] Manual testing on Android
- [ ] Manual testing on iOS (if applicable)
- [ ] Manual testing on Desktop (if applicable)
## Checklist
- [ ] Code follows project style guidelines
- [ ] Tests pass locally
- [ ] No breaking changes (or documented if present)
## Related Issues
Closes #[issue-number]
gh pr create \
--base main \
--head "$CURRENT_BRANCH" \
--title "<generated-title>" \
--body "<generated-description>" \
--assignee @me
Add --label, --reviewer flags as appropriate based on context.