Hidden quality gate that runs before showing "Done!" to user - ensures all tests pass, build succeeds, and requirements met before claiming completion
/plugin marketplace add timequity/vibe-coder/plugin install vibe-coder@vibe-coderThis skill inherits all available tools. When active, it can use any tool Claude has access to.
scripts/verify.pyPart of the hidden validation layer. User never sees this running, but it prevents false "Done!" claims.
Core principle: Never show success to user without evidence.
/mvp:deploy/mvp:add featureBEFORE showing success to user:
[ ] Tests pass (run full suite, not partial)
[ ] Build succeeds (no compilation errors)
[ ] No TypeScript/linting errors
[ ] Feature actually works (manual smoke test)
[ ] Security checks pass (from security-check skill)
[ ] Code review clean (from code-review-auto skill)
ALL must pass. ANY failure = fix silently, don't show error to user.
What user sees:
Adding login feature...
✅ Done! Check your preview.
What happens behind the scenes:
1. Generate login code
2. Run tests → 2 failures
3. Fix failures automatically
4. Run tests → pass
5. Run build → pass
6. Security check → pass
7. Code review → 1 minor issue
8. Fix issue automatically
9. All gates pass → show "Done!"
If gate fails and can auto-fix:
If gate fails and cannot auto-fix:
Run all checks programmatically:
python scripts/verify.py --path /project/path --language rust
python scripts/verify.py --path /project/path --json # JSON output
The script auto-detects language and runs appropriate checks.
Called by:
/mvp:build - Before showing preview/mvp:add - Before confirming feature added/mvp:deploy - Before deploymentUses:
User paid for "vibe coding" - they describe what they want, we handle how.
Showing them test failures or build errors breaks the magic.
Fix it. Don't explain it.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.