Vibe Skill
Purpose: Is this code ready to ship?
Loop position
Per-slice quality gate within move 6 (close the bead by proving acceptance) of the operating loop. Consumes a slice's changes; produces PASS/WARN/FAIL on complexity, architecture, security, intent fit. Vibe answers "is this slice ready to be counted against the slice-validation roll-up?" — it is not a substitute for the slice's first failing test (the test proves behavior; vibe judges the code that gets there).
Three steps:
Complexity analysis — Find hotspots (radon, gocyclo)
Bug hunt audit — Systematic sweep for concrete bugs
Council validation — Multi-model judgment
Quick Start
related skills
semantically similar in the cross-vendor index
don't have the plugin yet? install it then click "run inline in claude" again.
+clear positioning within operating loop (move 6) prevents scope creep and sets explicit boundary vs. test validation
+three-step procedure (complexity, bugs, council) is concrete enough to implement
+acknowledges it's a supplementary gate, not a replacement for test-driven behavior
weaknesses
~procedure is incomplete - names tools (radon, gocyclo) but doesn't define thresholds, pass criteria, or how council judgment works
~no explicit handling of failure modes (what if tools conflict? what if council is split?) or recovery paths
~trigger phrases missing entirely - how does a developer invoke vibe? what signals fire it?
