vibe

Import file or folder to .vibe/docs/ for reference - converts heavy formats, indexes automatically

Answer questions about this codebase using .vibe/ context and code search

Smart commit with test gate, .vibe/ sync, and optional PR creation

Full development workflow - explore, plan, implement, review, verify

Show available vibe commands and suggest next action based on project state

Analyze codebase and create .vibe/ context + debug/ test harness

1. Check `.vibe/` exists. If not: "No vibe context found. Run /vibe:init first."

End-to-end workflow with minimal stops - clarify, implement, review, present

Brainstorm, ask questions, create an implementation plan - then execute or save for later

Autonomous multi-task loop - decompose, implement and review each subtask, report results

Sync .vibe/ and debug/ after manual code changes outside vibe commands

Five-part adversarial review - code quality, bugs, functionality, risks, simplification

Test-driven development - write tests first, lock contract, implement until green

Implements code changes following project patterns exactly. Use when code needs to be written or modified.

Explores codebases to map architecture, patterns, and concerns. Use when you need to understand how code works before making changes.

Adversarial code review for bugs, security, functionality, and style. Use after code is written or modified.

Runs project tests, debug/ suite, and linters. Reports results with failure details. Use after code is written or modified.

Detects code risks and security issues during review, risk scanning, or code evaluation. Writes findings to risks.md with impact level and file:line references.

Auto-loads .vibe/ project context for commands and agents. Triggers on code questions, implementation, reviews, planning. Provides role-based context loading and API lookup chain.