vibe-safelisted

# vibe-safe ## Overview Active safety session for non-technical contributors. Claude reads your actual git state and scans real files — you don't self-report anything. Every flag cites the line and file. **Core rule: "Claude said it's fine" is not a safety check. This skill is.** ## Auto-routing You don't need to pick a mode. Just say `vibe-safe` and Claude will detect the right one: ``` git status shows no staged changes, you're describing a task → BEFORE mode git diff --staged has content → COMMIT mode git diff HEAD has unstaged changes → REVIEW mode "did Claude change more than I asked?" → SCOPE mode commits ahead of main, ready to open PR → PR mode conflict markers in any file → CONFLICT mode Claude just proposed something that feels big → ALARM mode "what does this flag mean?" / need deeper explanation → EXPLAIN mode developer reviewing a vibe-coded PR → REVIEWER mode checking whether past commits contain mistakes → HISTORY mode `.vibesafe` exists and repo has changed significantly → REFRESH mode ``` Or invoke directly: `vibe-safe before / review / scope / commit / pr / conflict / alarm / history / explain / reviewer / refresh` --- ## Repo Configuration: `.vibesafe` Two purposes: (1) custom danger/safe zones, (2) developer-defined contracts that vibe-safe enforces for every PM contribution. ``` # .vibesafe # ── Zones ──────────────────────────────────────────── danger_zone: src/payments/ danger_zone: infrastructure/ safe_zone: src/components/marketing/ safe_z