feature_flag_gatekeeper

Gate external API integrations and UI blocks behind feature flags.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/haulcommand-max/haul-command --skill feature-flag-gatekeeper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature_flag_gatekeeper
Source: https://github.com/haulcommand-max/haul-command/tree/main/skills/feature_flag_gatekeeper
Command: npx skills add https://github.com/haulcommand-max/haul-command --skill feature-flag-gatekeeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces gating of expensive or risky features behind a remote switch to prevent unintended live releases.

Core Features & Use Cases

  • Flag Definition: Check supabase/migrations/*_feature_flags.sql for existing keys, and if new, add an INSERT to the seed file; default enabled to FALSE.
  • Implementation Pattern: Use a reusable guard with a checkFlag wrapper to ensure expensive logic only runs when the flag is enabled, otherwise fall back to a safe path.
  • The "Billing Lock": If a feature costs money, the flag config must support a provider switch to toggle between paid and free paths.
  • Verification: Validate the fallback path by ensuring the app runs without an API key or external dependency when the flag is off.

Quick Start

Wrap external API usage with a feature-flag check to gate expensive logic behind a remote toggle.

Frequently Asked Questions about feature_flag_gatekeeper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I gate new integrations behind a feature flag to prevent unintended releases?

Gate new integrations by wrapping external API usage in a reusable checkFlag guard, ensuring expensive logic only runs when the flag is enabled, otherwise falling back to a safe path.

How do I add a new feature flag to my database migrations and seed defaults?

Check your supabase migrations for existing feature flag keys, and if new, add an INSERT statement to the seed file with the default enabled value set to FALSE.

What is the billing lock pattern for feature flags that cost money?

The billing lock requires the feature flag config to support a provider switch, allowing you to toggle between paid and free execution paths to prevent unintended billing.

How do I validate the fallback path when a remote switch is disabled?

Validate the fallback path by ensuring your application runs correctly without the external API key or dependency when the feature flag is set to off.

Can I use feature flag gating for major UI blocks during rollout?

Yes, you can apply feature flag gating to large UI blocks during development and rollout, using the same checkFlag wrapper to hide or reveal major interface changes safely.