vibesafe

majiayu000's avatarfrom majiayu000

Uses the Vibesafe MCP server to scan, compile, test, save, diff, and report status for Vibesafe units. Activate when the user asks to run vibesafe CLI commands (scan/compile/test/save/diff/status), regenerate code from specs, or inspect drift/checkpoints.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026
[Developer Tools]

When & Why to Use This Skill

The Vibesafe Claude skill integrates the Vibesafe MCP server directly into your AI environment, enabling seamless management of the Vibesafe toolchain. It empowers developers to automate complex CLI operations—such as scanning units, compiling code from specifications, and running quality gates—through natural language, significantly streamlining the development lifecycle and ensuring code-to-spec synchronization.

Use Cases

  • Automated Code Regeneration: Use the 'compile' tool to instantly update implementations based on updated specifications, ensuring your codebase remains consistent with design requirements.
  • Quality Assurance & Testing: Trigger 'test' commands to execute doctests and quality gates across specific units or the entire project to maintain high software standards.
  • Drift Inspection & Versioning: Utilize 'diff', 'save', and 'status' tools to monitor changes against checkpoints, inspect implementation drift, and manage the state of Vibesafe units.
  • Project Architecture Auditing: Quickly run 'scan' to list all registered units and their associated metadata, providing a clear overview of the project structure and dependencies.
namevibesafe
description"Uses the Vibesafe MCP server to scan, compile, test, save, diff, and report status for Vibesafe units. Activate when the user asks to run vibesafe CLI commands (scan/compile/test/save/diff/status), regenerate code from specs, or inspect drift/checkpoints."
version"0.2.1"
tags["vibesafe", "codegen", "mcp", "cli"]
allowed-tools"MCP(vibesafe:*)"

Vibesafe MCP Skill

Provides full control of the Vibesafe toolchain through the MCP server exposed by this plugin.

When to Use

  • User asks to run vibesafe scan, compile, test, save, diff, or status.
  • Need to regenerate implementations from specs or check drift against checkpoints.
  • Want to query registry contents, provider config, or checkpoints via the MCP tools.

Available Tools

  • 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).
  • status — report version, unit counts, environment.

Examples

  • “List all vibesafe units” → use scan.
  • “Recompile app.math.ops/fibonacci” → call compile with target.
  • “Run vibesafe tests” → call test.
  • “Save checkpoints for all units” → call save.
  • “Check drift” → call diff (via status+diff as available).