菜单
Generate a comprehensive pull request description with verification and impact details. Use when asked to create a detailed PR, write PR descriptions, prepare PRs for review, or generate PR documentation with change categorization, verification results, and impact analysis.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | pr-full |
| description | Generate a comprehensive pull request description with verification and impact details. Use when asked to create a detailed PR, write PR descriptions, prepare PRs for review, or generate PR documentation with change categorization, verification results, and impact analysis. |
| disable-model-invocation | true |
Generate a detailed pull request description that provides full context for reviewers, including change summaries, verification results, and impact analysis.
git log --oneline <base>..<head> to get commit history.git diff <base>..<head> or use gh pr diff to understand changes.fix, refactor, feat, etc.) and map to icon categories.## Summary
[Brief description of what this PR does and why — keep under 3 lines]
## Changes
### 🐛 Critical Bug Fixes
- **[Bug description]** — [Location/impact]
### ✨ Features
- **[Feature description]** — [Details]
### 🔧 Refactoring
- **[Change description]** — [Details]
### ⚡ Performance
- **[Change description]** — [Details]
### 📝 Documentation
- **[Change description]** — [Details]
### 🧹 Cleanup
- **[Change description]** — [Details]
## Verification
✅ [Check 1]: [Result]
✅ [Check 2]: [Result]
✅ [Check 3]: [Result]
## Commits
| Commit | Description |
| --------- | ---------------- |
| `abc1234` | [commit message] |
| `def5678` | [commit message] |
## Code Quality Improvements
| Metric | Before | After |
| ---------- | -------- | ------- |
| [Metric 1] | [Before] | [After] |
| [Metric 2] | [Before] | [After] |
## Breaking Changes
[None / List any breaking changes with migration notes]
## Testing
- [ ] Unit tests added/updated
- [ ] Integration tests pass
- [ ] Manual testing completed
- [ ] Edge cases handled
## Checklist
- [ ] Code follows project style guidelines
- [ ] Self-review completed
- [ ] Comments added for complex logic
- [ ] Documentation updated (if needed)
- [ ] No new warnings introduced
| Category | Icon | Usage |
|---|---|---|
| Critical Bug Fixes | 🐛 | Security issues, crashes, data loss |
| Bug Fixes | 🐛 | General bug fixes |
| Features | ✨ | New functionality |
| Refactoring | 🔧 | Code restructuring |
| Performance | ⚡ | Speed improvements |
| Documentation | 📝 | Docs changes |
| Testing | ✅ | Test additions/updates |
| Cleanup | 🧹 | Removal of dead code |
| Security | 🔒 | Security improvements |
| Dependencies | 📦 | Package updates |
| Configuration | ⚙️ | Config changes |
| Architecture | 🏗️ | Structural changes |
Orchestrates the full idea-to-ship workflow. Use when the user has a new idea, feature, or project and wants guided step-by-step progress. Triggers on "I have an idea", "let's build", "new feature", "start a project", or when the user wants to follow the complete workflow from concept to code.
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
Self-driving version of grill-with-docs. Runs an auto-grill loop (auto-selects recommended options without asking) while creating ADRs and glossary entries via domain-modeling as decisions resolve. Use when the user says "auto-grill with docs", "grill and decide with docs", or invokes /grill-with-docs-auto.
Long-running iterative development loops with pacing control and verifiable progress. Uses .scratch/<plan>/ structure where each plan has a PRD.md and issues/. Use when tasks require multiple iterations, many discrete steps, or periodic reflection with clear checkpoints; avoid for simple one-shot tasks or quick fixes.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.