菜单
Open a pull request for the current branch. Use when code is ready for review. Creates concise descriptions focused on the problem being solved.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Analyze unresolved PR review comments and recommend whether to fix, skip, or optionally address each. Use when a PR has review comments and you need a verdict on how to respond.
Create a git commit. Use when ready to commit changes. Creates conventional commit messages focused on why, not what.
Karpman Drama Triangle analysis for communication and conflict. Use when reviewing emails, proposals, or scripts for hidden drama dynamics, coaching difficult conversations, analyzing interpersonal conflict, or reframing victim/hero/villain patterns into Creator/Challenger/Coach alternatives.
Audit codebase, assess technical debt, analyze architecture, find structural problems. Use when evaluating code health, planning refactors, or need architectural review. Covers brittleness, coupling, complexity.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Interrogate a plan or design relentlessly — walk each branch of the decision tree and resolve every open decision until nothing vague remains. Use to stress-test a plan, surface edge cases and gaps you missed, get grilled on a design, or when you mention "grill me".
| name | create-pr |
| description | Open a pull request for the current branch. Use when code is ready for review. Creates concise descriptions focused on the problem being solved. |
| argument-hint | Optional branch name or --draft flag |
Create a high-quality PR for the current branch with a clear, concise description.
Run in parallel:
git diff main...HEAD --stat # Summary of all changes
git log main..HEAD --oneline # Commit history on this branch
git status # Check if pushed to remote
Before drafting, identify:
If the problem isn't clear from commit messages or code, stop and ask the user using AskUserQuestion. Never guess the problem statement.
## Summary
[2-3 sentences: what changed and why]
## Problem
[1-2 sentences: the user-facing issue or business need this solves]
---
Generated with [Claude Code](https://claude.com/claude-code)
Only add a Core Changes section for:
# Push if needed
git push -u origin HEAD
# Create PR (add --draft if requested)
gh pr create --title "type(scope): summary" --body "..."
Report the PR URL when complete.