add-feature-flag — Claude Code skill: what it does, how to install
add-feature-flag is a Claude Code skill that integrates feature flags into the Warp codebase. It isolates experimental code and manages rollouts across release channels.
AGPL-3.0 ★ 720 updated 2026-11-10
npx skills add dominikmartn/harp --skill add-feature-flag -a claude-codeWhat add-feature-flag does
This skill guides the agent through gating code changes inside the Warp terminal repository. It adds variants to the FeatureFlag enum in warp_core/src/features.rs and configures feature entries inside app/Cargo.toml. To test features early, developers register them inside the DOGFOOD_FLAGS array.
The FeatureFlag enum and runtime is_enabled() checks operate across both the desktop GUI and the headless TUI. Edits in app/Cargo.toml and app/src/lib.rs affect only the graphical client. If the terminal TUI requires a compile-time Cargo feature, it must be declared separately in crates/warp_tui/Cargo.toml and verified via ./script/run-tui.
The skill prioritizes runtime toggles over conditional compilation attributes. This reduces recompilation cycles and simplifies cleanup after launch. When attaching keyboard shortcuts via EditableBinding, adding an active check ensures hidden actions stay out of user settings while deactivated.
What it helps with
- declare a new feature flag within
warp_core/src/features.rs - gate unfinished changes behind runtime status checks
- enable pre-release features in dogfood builds
- hide custom keybindings when a feature remains disabled
Example prompts for the agent
- Add a feature flag for the new terminal block in the Warp repository
- Register my_experiment in DOGFOOD_FLAGS for internal testing
- Configure a keybinding check using the runtime feature flag status
How to install add-feature-flag
1Skills CLI (Vercel)
npx skills add dominikmartn/harp --skill add-feature-flag -a claude-code2Manually: put the files in place
~/.claude/skills/add-feature-flag/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/add-feature-flag/
1Skills CLI (Vercel)
npx skills add dominikmartn/harp --skill add-feature-flag -a codex2Manually: put the files in place
.agents/skills/add-feature-flag/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dominikmartn/harp --skill add-feature-flag -a cursor2Manually: put the files in place
.cursor/skills/add-feature-flag/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dominikmartn/harp .agents/skills/add-feature-flag2Manually: put the files in place
.github/skills/add-feature-flag/SKILL.md1Skills CLI (Vercel)
npx skills add dominikmartn/harp --skill add-feature-flag -a gemini-cli2Platform CLI
gemini skills install https://github.com/dominikmartn/harp --path .agents/skills/add-feature-flagManually: put the files in place
.devin/skills/add-feature-flag/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about add-feature-flag
How to install add-feature-flag in Claude Code?
Run npx skills add dominikmartn/harp --skill add-feature-flag -a claude-code. Alternatively, place the file at ~/.claude/skills/add-feature-flag/SKILL.md.
What does add-feature-flag do?
The skill instructs the coding agent on introducing feature flags into the Warp repository. It outlines updates to Cargo manifests, enum declarations, and runtime check enforcement.
How are feature flags tested inside the Warp TUI?
The FeatureFlag enum is shared across both front-ends, but TUI compile-time features need explicit declaration in crates/warp_tui/Cargo.toml. You can test this headless environment using ./script/run-tui.