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.
references/index.md
View on GitHub# VCO References Index
`references/` contains the maintained contributor and verification contracts.
Runtime truth lives in executable configuration and per-run artifacts.
## Start Here
- [`contributor-zone-decision-table.md`](contributor-zone-decision-table.md)
classifies repository surfaces before editing.
- [`change-proof-matrix.md`](change-proof-matrix.md) maps change classes to
the smallest required evidence.
- [`developer-entry-contract.md`](developer-entry-contract.md) defines the
stable contributor entry path.
- [`../config/live-document-contract.json`](../config/live-document-contract.json)
is the machine-readable live-document and artifact-sink contract.
## Adjacent Surfaces
- [CI proof](https://github.com/foryourhealth111-pixel/Vibe-Skills/actions/workflows/vco-gates.yml)
- [Latest GitHub Release metadata](https://github.com/foryourhealth111-pixel/Vibe-Skills/releases/latest)
- [`../scripts/verify/gate-family-index.md`](../scripts/verify/gate-family-index.md)
- [`../docs/README.md`](../docs/README.md)
## Rules
- Every maintained Markdown document under the governed roots is registered in
the live-document contract.
- Time-bound execution evidence belongs to the run artifact sink, CI, or a
formal release artifact.
- `bundled/skills` and legal/provenance material follow their separate
retention contracts.
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: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | 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: 323k | 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: 323k | Updated | Claude CodeCodex | Verified | Install |