What problem does it solve?
When a fix corrects wrong behavior, users see different numbers or charts without any explanation and mistake it for a regression. This Skill decides whether a change warrants an in-app notice and builds one that reaches only the affected users and can be removed later.
Core Features & Use Cases
- Gate criteria: Applies a four-condition test and a narrowing predicate so notices only reach users actually affected by the change.
- Five-part pattern: Provides an exported tested predicate, a feature flag in
lib/constants.tsx, a LemonBanner component returning null by default, an anchor at the shared render site, and a removal date.
- Copy and testing guidance: Supplies the two-clause copy shape (what changed, results may differ) and a parameterized unit test approach for the predicate.
- Use Case: After fixing date filter resolution on SQL insights, ship a dismissible banner above the visualization, flagged and predicate-gated, in the same PR as the backend change.
Quick Start
Ask the AI to evaluate whether your behavior-changing fix needs an in-app notice and, if so, generate the predicate, feature flag, banner component, and tests following this pattern.