write-vibe-tests

name	write-vibe-tests
description	Write or refactor Mistral Vibe tests with proper decoupling. Use when adding behavior coverage, testing ports/adapters, replacing brittle mocks, creating fakes, adding characterization tests before refactors, or changing tests under tests/ for vibe/core, vibe/cli, vibe/acp, tools, config, sessions, skills, hooks, MCP, or setup.
metadata	{"display-name":"Write Vibe Tests","short-description":"Write decoupled behavior tests for Vibe","default-prompt":"Use $write-vibe-tests to add or refactor Mistral Vibe tests around behavior and stable boundaries."}

Write Vibe Tests

Use this skill to make Vibe architecture testable, not just well-shaped. Tests should protect observable behavior while allowing internals to move.

Core Principle

Test behavior through stable boundaries. Do not couple tests to private methods, internal call choreography, or temporary structure.

If a refactor changes no observable behavior but breaks many tests, the tests are probably coupled to implementation details.

Vibe Test Boundaries

Code area	Preferred test boundary
Core use cases and services	Public function/class API, typed events, model outputs, persisted state
Tools	BaseTool.invoke/run, typed args/results, permission behavior, user-facing errors
LLM/backend orchestration	AgentLoop events and fake backend outputs
Config	Pydantic model validation, layer merge outputs, migration results