菜单
Review a GitHub Pull Request for code quality, architecture compliance, and project conventions using GitHub CLI. Approve if good, or request changes with specific feedback. Use when the user asks to review a PR, check a pull request, or approve a PR.
用 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.
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.
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.
| name | review-pr |
| description | Review a GitHub Pull Request for code quality, architecture compliance, and project conventions using GitHub CLI. Approve if good, or request changes with specific feedback. Use when the user asks to review a PR, check a pull request, or approve a PR. |
Review a Pull Request and submit an approval, request-changes, or comment via GitHub CLI.
Accept either:
123https://github.com/owner/repo/pull/123gh pr viewgh pr view <pr> --json number,title,body,author,state,commits,files,reviews,reviewDecision,mergeable,mergeStateStatus,isDraft
gh pr diff <pr>
gh pr checks <pr>
Review each changed file against these categories:
Code Quality
CancellationException)Architecture
StateFlow, combine, stateInCompose Multiplatform
expect/actual correctnessremember, derivedStateOf, stable keys)DisposableEffect)Testing
# PR Review: [Title]
**PR #**: [number] | **Author**: [username] | **Status**: [state]
## Summary
[High-level overview]
## Strengths
- [What was done well]
## Issues Found
### Critical
- [Security, crashes, data loss]
### Major
- [Logic errors, performance, bad patterns]
### Minor
- [Style, naming, docs]
## Suggestions
- [Improvements and alternatives]
## Testing Recommendations
- [Additional tests to add]
## Overall Assessment
**Approve** / **Request Changes** / **Comment**
[Reasoning]
Approve if ALL of the following are true:
Request Changes if ANY of the following are true:
Comment if only minor issues or questions remain.
# Approve
gh pr review <pr> --approve -b "<summary>"
# Request changes
gh pr review <pr> --request-changes -b "<summary>"
# Comment only
gh pr review <pr> --comment -b "<summary>"
Also post the full review as a PR comment:
gh pr comment <pr> --body "<full-review-markdown>"