What problem does it solve? Teams forget which tests should run after a change, and unmapped checks silently read as coverage. This Skill replaces agent memory with a deterministic .crew/verify.json map that a hook reads, so the decision of what to run is data-driven and reviewable. ## Core Features & Use Cases - Verification map authoring: Derive path-to-check rules from git history, verify each mapping by deliberately breaking code, and record the reasoning in a why field. - Safe credential handling: Record secret locations and retrieval commands in .crew/secrets.md without ever exposing values, preferring ephemeral containers and gitignored .env.smoke files over cloud secret stores. - Playwright and promotion gates: Set up tagged browser specs wired into the map, and define an environments block enforcing development-to-qa-to-production promotion with smoke, regression, and verify gates. - Use Case: After adding a database migration, the map automatically runs a fresh-database apply, a rollback test, and a round-trip check against a real database instead of relying on someone remembering to do it. ## Quick Start Ask the agent to build the verification map for this repository and wire the existing test directories into .crew/verify.json.
