القائمة
Use when the user wants to assess, unblock, and merge PRs. This is a human-facing convergence entrypoint that explains integration status and guides decisions, not an automated merge workflow.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user wants to classify dirty changes, create serial commits, split work into one or more PRs, or publish the current flow without merging it.
Use when the user wants to resume work on an existing branch or flow. Reads context, executes the next step, reviews the result, and reports to the user before proceeding. Equivalent to superpowers:executing-plans, using vibe3 as the execution backend.
Use when you need an overview of the Vibe Center project, its implementations (vibe2 shell and vibe3 python), the available commands, and the standard development workflow. This is the meta-skill that orients any agent to the project.
Use when starting or switching to a new human-collaboration task. Confirm the target issue, bootstrap the corresponding dev/issue flow scene, and hand off to the chosen implementation workflow. Do not use for resuming an existing branch; use vibe-continue instead.
Use after `scripts/install.sh` to guide users through machine-level setup, dependency checks, Claude/Codex toolchain readiness, and core feature introduction. Interactive onboarding for new users. Delegates diagnostics to `vibe doctor` and `vibe keys check`. Do not use for project-level configuration (use vibe-project-check instead).
Use after `vibe init` to verify target-project configuration completeness, tool availability, and environment readiness. Interactively prompts user to fill missing items. Orchestrates existing commands without adding Python code. Supports cross-project vibe3 readiness verification (Phase 5-8). Do not use for system-level installation issues (use vibe-onboard instead).
| name | vibe-integrate |
| description | Use when the user wants to assess, unblock, and merge PRs. This is a human-facing convergence entrypoint that explains integration status and guides decisions, not an automated merge workflow. |
该技能是人机协作的 PR 整合入口，负责解释当前状态、判断阻塞项、确认下一步。
vibe-integrate 只负责人机交互：
vibe-integrate 不承担的职责（由基础设施承接）：
这些集成语义由 vibe3 pr、vibe3 flow、CI 系统等基础设施承接。
底层基础设施应提供统一能力（供 vibe-integrate 消费）：
这些能力由 vibe3 CLI、gh CLI、CI 系统等提供，vibe-integrate 只负责解释和确认，不重新定义语义。
该 workflow 只描述人机交互步骤，不隐含自动化执行链语义。
优先读取基础设施提供的事实：
vibe3 flow show
vibe3 task status
确认：
open + had_pr 状态根据 PR 类型选择审核策略：
满足以下任一条件，跳过 review evidence 要求：
直接进入 Step 3。
涉及以下任一条件，必须有 review evidence：
检查：
@codex commentvibe3 review base判断合并条件（基于基础设施事实）：
LOC 超限场景（额外质量门）：
满足以下任一条件，除了 review evidence，还必须做一轮代码质量复查：
config/v3/loc_limits.yaml 阈值复查目标：
和用户确认阻塞项处理方案：
确认合并顺序（stacked PR 场景）：
记录本轮整合决策：
vibe3 handoff append "vibe-integrate: <summary>" --actor vibe-integrate --kind milestone
若 handoff 与当前真源不一致，必须在退出前修正。
该 skill 的最小停点：
Review evidence 可以来自：
vibe3 review base 本地 reviewvibe-integrate 负责统一解释这些 evidence，但不定义"哪种 evidence 更权威"的语义。
vibe-integrate 只负责人机交互，不定义 merge/readiness policy