foryourhealth111-pixel/Vibe-Skills
vibe
VerifiedVibe Code Orchestrator (VCO) is a governed runtime entry that freezes requirements, bounds execution, and enforces verification and phase cleanup.
scripts/README.md
View on GitHub# Scripts
`scripts/` 是 operator surface。这里只回答“该进哪个脚本目录”,不承担 proof contract 或长期 reference 导航。
## Start Here
- bootstrap / setup: [`bootstrap/one-shot-setup.ps1`](./bootstrap/one-shot-setup.ps1), [`bootstrap/one-shot-setup.sh`](./bootstrap/one-shot-setup.sh)
- operator actions: [`governance/README.md`](./governance/README.md)
- verify entrypoint: [`verify/README.md`](./verify/README.md)
- verify family map: [`verify/gate-family-index.md`](./verify/gate-family-index.md)
- shared helpers: [`common/README.md`](./common/README.md)
- router modules: [`router/README.md`](./router/README.md)
## Directory Roles
- `scripts/governance/`: rollout, release, audit, policy probes
- `scripts/build/`, `scripts/release/`: generated manifest and release-bundle materializers that were converged from the former root `tools/`
- `scripts/verify/`: executable gates and proof-producing checks
- `scripts/common/`: shared primitives and execution-context helpers
- `scripts/router/`: routing helpers and probes
- `scripts/bootstrap/`, `scripts/setup/`: install and environment setup
- `scripts/research/`: auxiliary support surfaces with exact-caller retention only
## Cross-Layer Handoff
- closure proof and current checks: [`verify/README.md`](verify/README.md) and
[`../config/live-document-contract.json`](../config/live-document-contract.json)
- long-lived contracts and ledgers: [`../references/index.md`](../references/index.md)
## Rules
- topology-aware scripts must run from the canonical repo root.
- packaging / release / compatibility changes后要回到 [`verify/README.md`](./verify/README.md) 复跑 gates。
- shared logic 进 `scripts/common/`,不要在单脚本复制 ad hoc helper。
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |