Plugin Stability Gate
Detect plugin regressions and roll back before they wreck a deadline
Third-party plugins can cause crashes, failed launches, or dramatic slowdowns after updates. This recipe adds change control to your plugin folder — tracking versions, logging failures, and enabling fast rollback when an update breaks your setup.
INGREDIENTS
PROMPT
Create a skill called "Plugin Stability Gate". Inputs: - plugin_paths - backups_path - notify_on_change (true) Behavior: - Watch plugin_paths for changes and record an inventory snapshot. - If I report crashes/slowdowns, ask what changed recently and guide me through isolating the offending plugin with a rollback plan.
How It Works
This skill takes periodic snapshots of your plugin inventory (name, version, path, last
modified) and watches for changes. When you report instability, it helps you isolate the
offending plugin through a structured test and provides rollback steps.
What You Get
- Plugin inventory snapshots: name, version, install path, last modified date
- Change notifications when plugins are added, updated, or removed
- Isolation test workflow: disable suspected plugin(s), relaunch, retry
- Rollback support from a "known good" plugin backups folder
- Crash packet: what changed, when, and step-by-step revert instructions
Setup Steps
- Add your plugin paths (e.g., Adobe MediaCore plug-ins folder)
- Set a backups path for storing known-good plugin versions
- Enable change notifications so you know when something is updated
- Optionally schedule monthly inventory snapshots
Tips
- Take a "known good" snapshot before installing any new plugin
- When crashes start, the first question is always: what changed recently?
- The isolation test (disable one plugin at a time, relaunch) is faster than reinstalling everything
- Check vendor release notes after each update — known issues are often documented before you hit them