Menu
提交 Pull Request。触发词："提交 PR"、"创建 PR"、"push"、"提交代码"、 "pr-worktree"。仅用于 xyz-pi-extensions 项目。
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | pull-request |
| description | 提交 Pull Request。触发词："提交 PR"、"创建 PR"、"push"、"提交代码"、 "pr-worktree"。仅用于 xyz-pi-extensions 项目。 |
当前在 worktree 目录中。可能有未提交的变更（会先 commit），也可能已全部 commit。
# 全量类型检查
pnpm -r typecheck
# 全量 lint
pnpm -r lint
# 全量测试
pnpm -r test
# 构建检查（无需产物，只确认不报错）
pnpm -r build --if-present 2>/dev/null || true
[MANDATORY] 零容忍：任何失败都必须正面修复，不允许跳过。
.githooks/pre-commit 执行相同的检查（tsc + eslint + vitest + pi manifest 校验），pre-merge 验证应与 githook 对齐。
git status --porcelain # 检查是否有未提交变更
git add -A && git commit -m "$COMMIT_MSG"[MANDATORY] 自动从分支所有 commit 生成，无需用户提供。全部使用英文。
流程：
git log main..HEAD --format="%s%n%b---"
git diff main..HEAD --stat
fix(scope): short summary 或 feat(scope): short summary（conventional commit 风格）fix: short summary 不带 scope## Summary 段落概括改动目的和内容## Changes 列表逐条列出各 commit 的关键改动（合并相关条目，不重复）## Test plan 列出验证方式（如已有的 typecheck/test/lint 结果）# push（force-with-lease 安全推送）
git push origin HEAD --force-with-lease
判断 PR 是否已存在：
gh pr list --head $(git branch --show-current) --state open --json number,title,body
PR 不存在：创建新 PR
gh pr create --title "$PR_TITLE" --body "$PR_BODY" --base main
PR 已存在：比较生成的 title/body 与现有 PR 的 title/body，仅在内容不同时更新
gh pr edit $PR_NUMBER --title "$PR_TITLE" --body "$PR_BODY"
pnpm -r）pnpm changeset 创建）validate-skill-yaml.py 校验 frontmattervalidate-extensions-yaml.py 校验| 标记 | 含义 | 修改约束 |
|---|---|---|
[MANDATORY] | 流程强制要求。不遵守会导致流程失败或产生严重后果 | 必须严格遵守 |
[OPTIONAL] | 可选步骤。可根据实际情况决定是否执行 | 可根据项目需求调整 |
完成 worktree 的完整合并流程：本地验证 → PR CI → merge → post-merge CI → 发布准备 → Release Notes → 创建 Release → 清理。 使用 git merge --no-ff 保留完整分支历史。 支持项目级钩子（.bare/custom-hooks/）实现个性化发布流程。 触发词："合并worktree"、"merge-worktree"、"合并PR"、"发布"、"release"、"上线"。
Reference for writing workflow JS scripts. Auto-loaded when using workflow-generate or writing/editing workflow scripts for Pi. Covers runtime environment, injected globals, constraints, and script patterns. Not for general coding or subagent usage.
Use when the user says "轻量执行", "lite execute", "按 Wave 执行", "goal 模式执行 plan", "执行 plan", or has a completed plan.md (from lite-plan) or execution-plan.md (from mid-detail-plan) and needs to execute the Waves. ADR-029 后阶段 A+B 由 workflow run execute-full-workflow 机器接管（worktree-setup → dev waves → test+review → cleanup），主 agent 不再直接派 subagent。 对应 CW action: dev (workflow 内 implementer 渐进式提交) + test (workflow 内 test-runner 渐进式提交). Not for planning (lite-plan / mid-detail-plan). Not for retrospect (coding-retrospect).
Use when the user says "issue拆分", "问题分解", "issue decomposition", "方案对比", "tradeoff analysis", "优先级排序", or has finished system-architecture.md and needs to break it into prioritized issues with solution comparisons. Produces issues.md as a fog-of-war decision map. Step 3 of 6. Not for business requirements (Step 1) or architecture modeling (Step 2). Not for non-functional risk analysis (Step 4) or code-level design (Step 5).
Use when the user says "mid 详细计划", "中等功能实施设计", "issues+nfr+架构+计划一起做", "批量设计实施", or has finished mid-plan and needs issues.md + non-functional-design.md + code-architecture.md + execution-plan.md (+ code-skeleton) + detail.json (CW detail action 入参). 纯设计 skill，不写实现代码。对应 CW action: detail. Not for L3 heavy (use full-*). Not for requirements/architecture (that is mid-plan).
[internal] Shared reference files for the lite workflow (lite-plan / coding-execute / coding-retrospect). Not invoked directly — sibling lite-* skills resolve paths via ../lite-shared/references/{file}.md. Kept hidden from model invocation.