promote-feature

Promotes a gated FeatureFlag from Dogfood to Preview and Stable in warp_core and app.

37|1|Updated Apr 28, 2026

Search Tags:#workflow #rust #cargo #release-management #software-engineering #rollout #feature-flag

Ready to run

npx skills add https://github.com/terzigolu/warp-lite --skill promote-feature-terzigolu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: promote-feature
Source: https://github.com/terzigolu/warp-lite/tree/main/.agents/skills/promote-feature
Command: npx skills add https://github.com/terzigolu/warp-lite --skill promote-feature-terzigolu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating staged promotion of gated features across runtime and compile-time boundaries, ensuring safe rollouts and traceable changes.

Core Features & Use Cases

Promote a FeatureFlag from Dogfood to Preview and then Stable with corresponding updates to runtime flags and Cargo features.
Maintain a safe rollback path by keeping the flag in place for 1–2 release cycles and scheduling cleanup with the remove-feature-flag workflow.
Align runtime (warp_core/src/features.rs) and compile-time (app/Cargo.toml, app/src/lib.rs) surface so builds and behavior match across channels.

Quick Start

Add the feature flag to DOGFOOD_FLAGS, then promote it through PREVIEW and Stable following the described steps.

Frequently Asked Questions about promote-feature

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

FAQPage Schema

How do I promote a feature flag from Dogfood to Preview and Stable in Rust?▼

To promote a feature flag, you coordinate staged updates across runtime and compile-time boundaries by modifying warp_core/src/features.rs, app/Cargo.toml, and app/src/lib.rs to align builds and behavior across channels.

What is the safest way to roll out a gated Cargo feature to a broader audience?▼

The safest rollout method maintains a safe rollback path by keeping the feature flag in place for 1–2 release cycles, allowing you to revert behavior without immediate code deletion before scheduling cleanup.

Why do I need to update both runtime flags and Cargo features during a release rollout?▼

Updating both runtime flags and Cargo features ensures that compile-time and runtime surfaces match across channels, preventing discrepancies where builds and behavior diverge during the staged promotion process.

When should I clean up a feature flag after a staged promotion?▼

You should schedule cleanup after keeping the flag for 1–2 release cycles to ensure a safe rollback window, utilizing the remove-feature-flag workflow to completely remove the gated feature.

Does promoting a feature flag require changes to app/Cargo.toml and app/src/lib.rs?▼

Yes, promoting a gated feature enforces changes to app/Cargo.toml and app/src/lib.rs to bridge cargo features with runtime flags, ensuring builds and behavior match across channels.

Can I use this staged promotion approach for Rust projects without a rollback window?▼

No, this approach specifically applies to scenarios requiring a safe rollback window by keeping the flag for 1–2 release cycles before scheduling cleanup with the remove-feature-flag workflow.