vibekit

vibekit

Vibekit is a discipline-first vibe-coding plugin for Claude Code, OpenAI Codex, OpenCode, Gemini CLI, and Pi. One command — /vibe <intent> — drives a 7-stage pipeline (brainstorm → plan → isolate → exec → verify → review → integrate) that produces a verified, user-approved feature. For autonomy, /ralph-loop re-runs /vibe across iterations until verify-gate is satisfied, bounded by budgets, and never bypassing sign-off.

Token-efficient per feature: subagent briefs are RTCO-compressed and reports are schema-stripped, while every guardrail — evidence quotes, plans, constraints, degradation warnings — stays verbatim.

Guardrails are non-negotiable. If the plan is wrong or the tests don't pass, the pipeline halts loudly — it does not silently commit the wrong thing.

---

What you get

• /vibe <intent> — the full 7-stage pipeline in one command.
• /ralph-loop <intent> — autonomous bounded re-run of /vibe with a blocker classifier and thrashing critic. Same gates, never bypasses sign-off.
• Fourteen invocable skills that also work standalone, plus an auto-loaded priming layer (using-vibekit) that carries the trigger map.
• Auto-trigger discipline. A SessionStart hook (Claude Code) and equivalent adapters (Codex native discovery, Gemini @-import, opencode plugin, Pi before_agent_start extension) load using-vibekit into every session so pipeline skills cannot be silently skipped.
• Evidence-based verification. Every "done" claim is backed by the exact test output, verbatim.
• Halt-and-report discipline. Real live eval caught two plan defects cleanly; neither reached a commit.
• Token-efficient by design. Compression is applied to agent framing; every guardrail stays verbatim.
• Karpathy-aligned discipline. Four-axis authoring contract: PEG (substance), Karpathy (behavior), Caveman (style), Quad-Adapter (cross-runtime portability).
• Parallel-group dispatch when a plan marks tasks as independent, with honest sequential fallback on runtimes that lack parallel subagents.
• Cross-session knowledge. memory-dual captures durable project knowledge — atomic facts, compound documents, and a working notepad — under one file-backed convention.

---

Install

Claude Code

From a marketplace that hosts this plugin:

/plugin marketplace add rizukirr/vibekit
/plugin install vibekit@vibekit

From a local clone:

git clone <this repo>
cd vibekit
# then add the repo path as a plugin source in Claude Code settings

After installation, restart Claude Code. The /vibe command and all skills become available.

OpenCode

Tell the agent:

Fetch and follow instructions from https://raw.githubusercontent.com/rizukirr/vibekit/refs/heads/main/.opencode/INSTALL.md

That keeps installation instructions centralized in one file and avoids README drift.

OpenAI Codex

Install with:

codex plugin marketplace add rizukirr/vibekit
codex plugin add vibekit --marketplace vibekit

Detailed Codex docs are in .codex/INSTALL.md.

Gemini CLI

Tell Gemini CLI:

Fetch and follow instructions from https://raw.githubusercontent.com/rizukirr/vibekit/refs/heads/main/INSTALL.gemini.md

Detailed Gemini docs: INSTALL.gemini.md.

Pi

Tell Pi:

Fetch and follow instructions from https://raw.githubusercontent.com/rizukirr/vibekit/refs/heads/main/.pi-plugin/INSTALL.md

Manual installation is also documented in .pi-plugin/INSTALL.md.

Quick install (global settings):

pi install git:github.com/rizukirr/vibekit

Install into project settings (.pi/settings.json) instead of global settings:

pi install git:github.com/rizukirr/vibekit -l

Useful maintenance commands:

pi list
pi update
pi remove git:github.com/rizukirr/vibekit

Heads-up — possible conflict if vibekit is already installed. Pi reads skills from ~/.agents/skills/ as well as Pi package sources. If you previously installed vibekit for another runtime (commonly Codex, which symlinks ~/.agents/skills/vibekit/), Pi can already see every vibekit skill from that path, and installing again can produce benign "skill collision" warnings on startup. Check first:

ls ~/.agents/skills/vibekit/ 2>/dev/null

If that lists 15 skill directories, vibekit is already reachable on Pi via /skill:<name>. Skip pi install to avoid collision warnings, or follow the "Avoiding collisions" guidance in .pi-plugin/INSTALL.md.

---

Quick start

/vibe add a toKebabCase utility with tests

What happens: