add-feature-flag
Add a new feature flag to gate code changes in the Warp codebase.
Install
With your agent
Install OMGSkills skill "warpdotdev/warp:.agents/skills/add-feature-flag" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/warpdotdev/warp /tmp/warp && ln -s /tmp/warp/.agents/skills/add-feature-flag ~/.claude/skills/add-feature-flagFrom README
add-feature-flag Add a new feature flag to gate code changes in the Warp codebase. Overview Feature flags in Warp are compile-time flags that allow features to be selectively enabled for different channels (e.g.: Dev, Stable). They use a small runtime plumbing layer that checks if a flag is enabled. TUI note The FeatureFlag enum (warpcore/src/features.rs) and the runtime FeatureFlag::X.isenabled() check are SHARED by both front-ends: the GUI desktop app (app/) and the headless TUI (crates/warptui). The Cargo-feature steps in this skill (app/Cargo.toml, app/src/lib.rs) are GUI-app-specific. Prefer runtime isenabled() checks so a flag works in both front-ends with no per-binary wiring. Only if you truly need a compile-time Cargo feature in the TUI, wire it into crates/warptui/Cargo.toml as well. Test the TUI with ./script/run-tui.
More from this repo
factory-files
Used to create and edit file-based Warp software factory definitions, in a repository tree rooted at a factory.yaml.
factory-mcp
Use the Warp Factory MCP to hand work to a software factory and collaborate with it — bundle local work and send it to...
add-telemetry
Used to add telemetry events to track user behavior or system events in the Warp codebase.