菜单
Use when the user asks to create, open, or raise a GitHub pull request, submit changes for review. Also when staged, committed, or unpushed work needs a PR via gh CLI and required PR metadata is missing (base branch, draft vs ready, reviewers, labels, linked issues, test plan).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user asks to commit, write a commit message, generate a conventional commit, or invokes /conventional-commit. Also use when staged changes need a commitlint-compliant message, when the user asks to commit and push (or passes --push), when unstaged or untracked files exist and staging scope must be confirmed, or when agent-attribution trailers must be avoided on commits. Handles git commit and git push flags when the user passes them.
Use when the task is multi-constraint, ambiguous, architectural, or needs a design/algorithm choice before answering. Skip for trivial lookups and one-line edits.
Use when the user explicitly asks to audit, critic, or verify a generated solution or answer (e.g. /verifying-solutions, "audit this", "critic this") — not for routine completion claims or pre-answer design.
Use when staging, formatting, or creating git commits for code changes in a Git repository.
Analyzes error logs, stack traces, and provides systematic debugging strategies and solutions
Drafts professional emails based on context, tone, and purpose with templates and suggestions
| name | grill-pr |
| description | Use when the user asks to create, open, or raise a GitHub pull request, submit changes for review. Also when staged, committed, or unpushed work needs a PR via gh CLI and required PR metadata is missing (base branch, draft vs ready, reviewers, labels, linked issues, test plan). |
Interview the user through every PR decision, then create the pull request via gh.
Load and follow WORKFLOW.md.
skip grilling — final approval is never skipped.git diff ${BASE}...HEAD, not just the latest commit.conventional-commit (never invent messages inline).git add . / git add -A.gh pr create if present in draft or template.| Phase | Action |
|---|---|
| 0 | Confirm repo (multi-root) |
| 1 | Parallel git audit → Preflight summary |
| 2 | Resolve PR template |
| 3 | Draft title + body into template |
| 4 | Grill — decision-tree.md + ask-question.md |
| 5 | Push (if approved) + gh pr create |
| 6 | Return PR URL |
--title instead of PR body| Excuse | Reality |
|---|---|
| "User said create PR so just do it" | Grilling mandatory unless skip grilling |
| "I'll ask about test plan in the body" | Test plan is decision tree node |
| "Only latest commit matters" | Must use git diff base...HEAD |
| "Summary + Test plan is good enough" | Repo template first; fallback only if none |
| "I'll web search every PR" | Fallback is pre-researched in references |
| "Pushing is implied for PR" | Requires explicit approval |
| "AI attribution is harmless branding" | Forbidden — strip before create; company PRs stay product-neutral |
| "Long title is more descriptive" | Body holds detail; title ≤72 chars single-line conventional header |
| "72 chars is too short" | GitHub UI wrap is worse; shorten scope/subject per pr-title.md |
| "User already answered in chat" | question tool unless they picked that option in the same question flow |
| "Body edits need open conversation" | Other option → prose edit → resume question for next node |