Stats
Actions
Tags
From vibesafe
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vibesafe:skills/vibesafeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Provides full control of the Vibesafe toolchain through the MCP server exposed by this plugin.
Provides full control of the Vibesafe toolchain through the MCP server exposed by this plugin.
vibesafe scan, compile, test, save, diff, or status.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.scan.compile with target.test.save.diff (via status+diff as available).npx claudepluginhub julep-ai/vibesafe --plugin vibesafeDiagnoses vibekit installation health—skill file integrity, registration parity, directory structure. Reports verdict; `--fix` auto-repairs safe items.
Runs all skills in parallel across a repository, synthesizing findings into a prioritized report. Invoke via /vibesubin for full sweeps, routes vague requests, and fast-paths security incidents like leaked secrets.
Audits Claude Code project configuration for drift and collaboration issues across six layers (CLAUDE.md, rules, skills, hooks, subagents, verifiers), tiered by project complexity.