القائمة
Sync vibe-doctor harness/template updates while preserving project-owned code and rules.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Update durable context shards and run checkpoint validation when project rules, architecture, workflows, or long-running Orchestrator state changes.
Codex-compatible wrapper for the shared vibe-doctor context maintenance and Orchestrator checkpoint workflow.
Convert a fully settled design into repeated /goal + $vibe-iterate implementation cycles. Use when the user has finished a detailed design discussion, says there are no more open questions, and wants Codex to autonomously split the design into items, run mini planning/interview checkpoints only when needed, generate Planner/Sprint work, implement each item, verify it, persist handoffs/checkpoints, and continue non-stop until every item is complete or a real blocker is found.
Codex-compatible wrapper for the shared vibe-doctor goal-iteration workflow. Use when a settled design needs autonomous itemized /goal plus $vibe-iterate implementation cycles until every item is completed, blocked, or deferred with durable handoffs.
프로젝트 초기 세팅을 대화형으로 진행합니다. 환경 점검, provider 인증, 프로젝트 맞춤 설정까지 자동으로 안내합니다.
Codex-compatible wrapper for the shared vibe-doctor project initialization workflow.
| name | vibe-sync |
| description | Sync vibe-doctor harness/template updates while preserving project-owned code and rules. |
/vibe-sync updates harness-owned files from upstream according to .vibe/sync-manifest.json. It must preserve project-owned source, product context, local provider settings, and PROJECT:* marker blocks.
/vibe-sync or npm run vibe:sync.npm run vibe:sync -- --dry-run and inspect the plan.conflict rows to the user unless they already authorized forceful sync.npm run vibe:sync..vibe/harness/tsconfig.harness.json.vibe/harness/scripts/vibe-preflight.mjs --bootstrap.vibe/sync-backup/<timestamp>/ for recovery context.Run this before and after changing sync boundaries or the sync runbook:
npm run vibe:sync-audit
The audit must pass before release because /vibe-sync is allowed to replace
harness-owned files across downstream projects. It verifies that the manifest
does not move project-owned source, context, runtime state, provider settings,
or product scripts into harness ownership.
| Flag | Purpose |
|---|---|
--dry-run | Print the plan only. |
--force | Replace all conflicted harness files with upstream versions. |
--from <path> | Use a local upstream checkout instead of cloning. |
--ref <tag> | Override the upstream git ref for this run. |
--no-backup | Skip backup creation. |
--no-verify | Skip post-sync typecheck/preflight. |
--json | Print the plan as JSON. |
For old projects that cannot run the normal sync path yet, run the standalone bootstrap once from the project root. It understands current glob-based manifests and copies .vibe/harness/** before normal /vibe-sync is available.
Local clone:
git clone --depth 1 https://github.com/mir3626/vibe-doctor /tmp/vibe-doctor
node /tmp/vibe-doctor/.vibe/harness/scripts/vibe-sync-bootstrap.mjs
Compatibility raw URL, kept for legacy docs:
curl -sL https://raw.githubusercontent.com/mir3626/vibe-doctor/main/scripts/vibe-sync-bootstrap.mjs | node --input-type=module -
The root scripts/vibe-sync-bootstrap.mjs file is only a compatibility bridge. The canonical harness runtime lives under .vibe/harness/**.
vX.Y.Z or X.Y.Z: hard pin^vX.Y.Z or ^X.Y.Z: floating compatible rangemain: use as-isupstream.ref: use cached latest when newer than installed, then current harnessVersion, then mainDefault templates use caret refs so plain /vibe-sync advances to the latest compatible harness version. Use exact refs only when an intentional pin is needed.
src/**, scripts/**, test/**, app/**, components/**, and lib/** are project-owned after v1.7.0..vibe/harness/**.CLAUDE.md, AGENTS.md, GEMINI.md) stay hybrid through marker blocks. Root README.md is not full harness-owned; use a future marker strategy before syncing project README content.package.json sync owns scripts.vibe:* and engines; product scripts such as test, build, typecheck, and test:ui are project-owned.