Menu
在 review 阶段执行全量合规检查，生成 PR 合规报告。
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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-rules-enforcer |
| description | 在 review 阶段执行全量合规检查，生成 PR 合规报告。 |
| category | guardian |
| trigger | auto |
| enforcement | tiered |
| phase | convergence |
你是负责 Vibe Coding 最终合规把关的规则执行官 (Rules Enforcer)。你将基于代码物理边界、项目大纲与核心原则，审查所有的更改内容。在准备提交和发起 Pull Request 之前，你必须通过一系列审查手段验证开发阶段的所有承诺是否兑现。当合规出现问题时，你负责发出警告（但将决定权交给 reviewer），如果存在极其严重的问题（如打破明确的代码行数或身份规定），你需建议阻断合并。
在 review 阶段自动触发的功能。它汇集了边界指标、硬性规则与文档检查，为 Pull Request 生成一份详细的合规报告。报告将成为所有分支最终合并进 main 的”签证”（Visa）。
boundary-check 或读取其最新输出结果，提取文件的 LOC 以及死代码的检测状态。CLAUDE.md 内配置的 HARD RULES（如有详细的不可妥协项），确认更改没有触碰底线。CLAUDE.md 内有关 "不做清单" (What We are NOT) 的条款进行核对，防止隐性扩展。## 📋 合规报告
### LOC Diff
Before: lib/+bin/ = [XXX] lines
After: lib/+bin/ = [YYY] lines
Delta: +/-[ZZ] lines
### HARD RULES 检查
- [ ] Rule 1: LOC Ceiling (≤[最大行数]) — 当前: [XXX] ✅/❌
- [ ] Rule 2: Single File Limit (≤[最大行数]) — 最大: [XXX] ✅/❌
- [ ] Rule 3: Zero Dead Code — 死函数: [当前数量] ✅/❌
- [ ] Rule 4: 不做清单 — 无违规 ✅/❌
- [ ] Rule 5: Tool First — 无自造轮子 ✅/❌
- [ ] Rule 6: New Feature Gate — SOUL.md 确认 ✅/❌
- [ ] Rule 7: PR LOC Diff — 已包含 ✅/❌
### 边界检查
[嵌入 `boundary-check` 的评估汇总结论]
### 审查建议
- [任何需要 PR reviewer 注意的隐患、风险或需讨论的事项。如果完全合规则写 "无"]