vc-guardlisted

In-flight enforcer sibling of vc-trust. Inventories existing gates (commit-msg, pre-commit, pre-push, loctree-first, classifier hard-stops, commit-msg-diff advisory, trust-block dispatch refuse) and ships one fail-closed proof path: refuse workflow continuation when the trust journal records block for HEAD. Guard never invents settlement letters or re-judges claims. Trigger: "guard", "vc-guard", "gate inventory", "refuse on trust block".
vetcoders/vibecrafted · ★ 1 · AI & Automation · score 63

Install: claude install-skill vetcoders/vibecrafted

# vc-guard — the gate enforcer (not the judge) `vc-guard` is the **strażnik** sibling of `vc-trust`. Trust observes and judges after the fact on the Living Tree. Guard **enforces at the gate**. | Role | Skill | When | Mutates code? | Blocks dispatch? | Writes settlement? | | ------------- | ----------------- | --------- | ------------- | -------------------------- | ------------------------------ | | Judge | `vc-trust` | post-hoc | never | never | yes (only via explicit `note`) | | Enforcer | `vc-guard` | in-flight | never | **yes** (on trust `block`) | **never** | | Message shape | `commit-msg` hook | at commit | never | commit only | never | Do **not** mix these roles. Guard does not re-run falsification. Trust does not refuse launch. ## Canonical Structural Gate Before a `vc-guard` skill worker inventories gates or reports an enforcement decision, run or consume the `vc-init` procedure for the assigned repository. Pin the branch, HEAD, dirty state, runtime owner, and trust-journal path. A bare `guard check` is a narrow journal decision; it is not a substitute for repository orientation. Use `Loctree:loctree` as the default structural layer to produce or refresh the Code-Derived Application Map of the real enforcement line: hook entrypoints, `enforce_continuation` callers, journal readers,