vibesafe

Control the Vibesafe toolchain via MCP server for unit lifecycle operations.

3|Updated Oct 30, 2025
One-click install
npx skills add https://github.com/julep-ai/vibesafe --skill vibesafe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibesafe
Source: https://github.com/julep-ai/vibesafe/tree/main/skills/vibesafe
Command: npx skills add https://github.com/julep-ai/vibesafe --skill vibesafe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the Vibesafe MCP-powered workflow to scan, compile, test, save checkpoints, and report status for Vibesafe units. Activate when you want to run vibesafe CLI commands (scan/compile/test/save/diff/status), regenerate code from specs, or inspect drift and checkpoints.

Core Features & Use Cases

  • Scan: List all registered Vibesafe units with metadata.
  • Compile: Generate implementations for a unit (supports target, force).
  • Test: Run doctests/quality gates (optional target).
  • Save: Activate checkpoints (optional target).
  • Diff: Check drift against checkpoints.
  • Status: Report version, unit counts, and environment.
  • Regenerate implementations from specs or verify drift against checkpoints.

Quick Start

Use the vibesafe skill to run common operations like:

  • Scan all units: vibesafe scan
  • Recompile a unit: vibesafe compile --target app.math.ops/fibonacci
  • Check drift or status: vibesafe diff or vibesafe status

Frequently Asked Questions about vibesafe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan and list all Vibesafe units?

Scan lists all registered Vibesafe units with their metadata in a single command. Run `vibesafe scan` to display the complete inventory of units available in your registry, which serves as the foundation for all downstream operations like compilation and testing.

How do I generate implementations from Vibesafe specs?

Compile generates implementations for Vibesafe units from their specifications. Use `vibesafe compile` to produce code, optionally targeting specific units with `--target` or forcing regeneration with `--force` to overwrite existing implementations.

How do I check for drift between code and checkpoints?

Diff detects drift by comparing current unit implementations against saved checkpoints. Run `vibesafe diff` to identify deviations from the last saved state, helping you track unintended changes or verify spec compliance across your codebase.

Can I automate testing and validation for Vibesafe units?

Test runs doctests and quality gates on Vibesafe units to validate implementations. Execute `vibesafe test` with an optional `--target` to run validation on specific or all units, ensuring generated code meets quality standards before checkpoint activation.

What does the Vibesafe MCP toolchain do?

Vibesafe is an MCP-powered toolchain that automates the full lifecycle of code units—scanning, compiling from specs, testing, saving checkpoints, and detecting drift. It integrates CLI commands with registry and provider configuration management via MCP.

How do I save and manage Vibesafe checkpoints?

Save activates checkpoints to record the current state of Vibesafe units as a baseline. Use `vibesafe save` with optional `--target` to persist unit versions, creating reference points for drift detection and change tracking in your workflow.