compliance-diff

Launch readiness decays. A month after a clean review, someone adds a session-replay tool, a signup field, or a /admin route. This skill reads a change and says what it re-opens.

Activate when

• A PR, branch, or release diff is under review, or the user asks "what does this change do to our launch/privacy posture?"
• A context note (.readyvibe/context.md), if one exists, has "NOT APPLICABLE" items whose recheck triggers might have fired.
• Not for a first full review (use launch-all).

Inspect

Get the diff (git diff <base>...HEAD, or the PR files). Look for these introductions, in order of consequence: