Management Talk
thananon/9arm-skills
Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA…
Remove a Ledger Wallet feature flag while preserving its resolved production behavior, then validate, create a draft PR, and watch CI to green.
MITAuto-check passed
Install Remove Feature Flag
$ npx skills add LedgerHQ/ledger-live --skill remove-feature-flag -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LedgerHQ/ledger-live remove-feature-flag --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LedgerHQ/ledger-live.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/remove-feature-flag .claude/skills/remove-feature-flag && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "remove-feature-flag" agent skill from https://github.com/LedgerHQ/ledger-live/tree/develop/.agents/skills/remove-feature-flag into .claude/skills/remove-feature-flag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-feature-flag", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LedgerHQ/ledger-live/tree/develop/.agents/skills/remove-feature-flagType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LedgerHQ/ledger-live --skill remove-feature-flag -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LedgerHQ/ledger-live remove-feature-flag --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LedgerHQ/ledger-live.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/remove-feature-flag .agents/skills/remove-feature-flag && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "remove-feature-flag" agent skill from https://github.com/LedgerHQ/ledger-live/tree/develop/.agents/skills/remove-feature-flag into .agents/skills/remove-feature-flag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-feature-flag", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LedgerHQ/ledger-live --skill remove-feature-flag -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LedgerHQ/ledger-live remove-feature-flag --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LedgerHQ/ledger-live.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/remove-feature-flag .cursor/skills/remove-feature-flag && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "remove-feature-flag" agent skill from https://github.com/LedgerHQ/ledger-live/tree/develop/.agents/skills/remove-feature-flag into .cursor/skills/remove-feature-flag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-feature-flag", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LedgerHQ/ledger-live.git --path .agents/skills/remove-feature-flag--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LedgerHQ/ledger-live --skill remove-feature-flag -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LedgerHQ/ledger-live remove-feature-flag --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LedgerHQ/ledger-live.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/remove-feature-flag .gemini/skills/remove-feature-flag && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "remove-feature-flag" agent skill from https://github.com/LedgerHQ/ledger-live/tree/develop/.agents/skills/remove-feature-flag into .gemini/skills/remove-feature-flag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-feature-flag", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LedgerHQ/ledger-live remove-feature-flagInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LedgerHQ/ledger-live --skill remove-feature-flag -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LedgerHQ/ledger-live.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/remove-feature-flag .github/skills/remove-feature-flag && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "remove-feature-flag" agent skill from https://github.com/LedgerHQ/ledger-live/tree/develop/.agents/skills/remove-feature-flag into .github/skills/remove-feature-flag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-feature-flag", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LedgerHQ/ledger-live --skill remove-feature-flag -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LedgerHQ/ledger-live remove-feature-flag --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LedgerHQ/ledger-live.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/remove-feature-flag .opencode/skills/remove-feature-flag && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "remove-feature-flag" agent skill from https://github.com/LedgerHQ/ledger-live/tree/develop/.agents/skills/remove-feature-flag into .opencode/skills/remove-feature-flag/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "remove-feature-flag", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
remove-feature-flag- GitHub stars
- 621
- Token cost
- ~1.4k tokens
- SKILL.md length
- 766 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- MIT
At a glance
Remove a Ledger Wallet feature flag while preserving its resolved production behavior, then validate, create a draft PR, and watch CI to green.
- Works in 7 steps: Resolve the production behavior → Protect local work and create the branch → Resolve Jira context → …
- SKILL.md covers Invocation, 1. Resolve the production…, 2. Protect local work and… and 3. Resolve Jira context, plus 4 more sections
- Runs JavaScript scripts from its folder; calls node
What it does
Remove Feature Flag is an agent skill from LedgerHQ/ledger-live. Remove a Ledger Wallet feature flag while preserving its resolved production behavior, then validate, create a draft PR, and watch CI to green. Invoke only through /remove-feature-flag; this command may stash local work, push a new branch, create or update Jira work, and publish a PR.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts.
It works with Jira and Firebase. The repository describes itself as: Mono-repository for Ledger Wallet apps and related packages. The licence is MIT.
Example prompts
- “/remove-feature-flag”
Requirements
- Node.js
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a3861a2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Remove Feature Flag loads about 1.4k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 766 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from LedgerHQ/ledger-live at commit a3861a2, republished under its MIT licence (© LedgerHQ). 766 words, ~1,450 tokens.
Download SKILL.mdSave it as
.claude/skills/remove-feature-flag/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- remove-feature-flag
- description
- Remove a Ledger Wallet feature flag while preserving its resolved production behavior, then validate, create a draft PR, and watch CI to green. Invoke only through /remove-feature-flag; this command may stash local work, push a new branch, create or update Jira work, and publish a PR.
- disable-model-invocation
- true
Remove Feature Flag
Run the complete removal workflow. Never write to Firebase.
Invocation
/remove-feature-flag <FEATURE_ID> [FLAG_VALUE_JSON] [TICKET_URL]Optional modifiers:
proposal only— analyze and propose without changing filesno pr— implement and validate without publishingno watch— create the PR without waiting for CI
Only FEATURE_ID is required. Treat invoking this command as authorization for
the complete workflow unless a modifier limits it. Accept optional arguments in
any trailing order: recognize the JSON object, an http(s) ticket URL, and the
exact modifier phrases independently.
For proposal only, stop after read-only analysis. Do not create Jira work,
stash files, create a branch, commit, push, or publish a PR. Report the resolved
behavior, owner, affected scope, proposed edits, planned validation, and skipped
Jira/PR/CI actions.
1. Resolve the production behavior
Derive the Firebase key with the repository's canonical snake-case mapping.
- Parse and use
FLAG_VALUE_JSONwhen supplied. Validate it against the flag definition and consumers. If it is invalid, lacks a booleanenabled, or omitsparamsthat code consumes, ask for a corrected production value. - Otherwise run:
bash node .agents/skills/remove-feature-flag/scripts/read-production-flag.mjs "$FEATURE_ID" - If the lookup is unavailable, missing, malformed, or unauthorized, ask the user for the production value. Never fall back to development.
- If Firebase reports conditional values, or the JSON describes A/B variants, show them and ask which behavior to preserve. Do not choose a client-specific variant automatically.
Preserve the resolved production behavior whether enabled is true or
false, including the selected production params.
2. Protect local work and create the branch
Record the initial branch/ref and worktree state. If dirty, stash staged, unstaged, and untracked files with a unique descriptive message; do not ask.
Fetch the latest remote base and always create a new branch:
support/remove-<feature-id>-flag-<YYYYMMDD-HHmm>Create it directly from the freshly fetched origin/develop. If the name
collides, append a numeric suffix. Never reuse an existing branch or PR.
3. Resolve Jira context
Identify the owning team from flags/team-* and CODEOWNERS; use the
codeownership skill when a team directory is involved.
When no ticket is supplied and Jira tools are available:
- Search the owning team's backlog by feature id and Firebase key.
- Reuse one clearly relevant removal ticket; ask if several match.
- If none match, create an unassigned
Taskin projectLIVEfor the owning team.
If Jira is unavailable, continue without a ticket and add this to the PR
description: No Jira linked: Jira access was unavailable during PR creation.
4. Remove the flag
Search tracked source across the whole repository for the feature id and Firebase key; ignore generated and build artifacts. Load and use all applicable repository skills for the files involved.
- Delete the flag definition and barrel export.
- Remove legacy
types-live, defaults, devtools, analytics, E2E, mocks, and test references when present. - Inline only the selected production behavior; remove unreachable branches.
- Update focused tests and snapshots without weakening coverage.
- Keep the change isolated from unrelated cleanup.
Firebase remains read-only. Add a post-release PR note to delete the remote key manually.
Show full SKILL.md (279 more words)Show less
5. Validate and publish
Use cleanup and run-tests for the affected packages and files, including
@shared/feature-flags checks when its registry changes. Follow
docs/validate-before-finishing.md. When those skills do not map a shared/,
features/, domain/, or nested package, read its README and package.json
and run the equivalent scoped commands directly.
Unless no pr is set, invoke create-pr end-to-end as the single source of
truth for Git conventions, changesets, commits, push, draft PR content, browser
opening, and the generated (not posted) Slack message. Pass it the resolved
behavior, Firebase key, Jira result, validation evidence, affected flows, and
the manual Firebase cleanup note.
For no pr, follow git-conventions, create a local commit after validation, and
do not push. Preserve that commit on the removal branch before restoring the
initial workspace.
6. Watch CI
Skip this section for no pr or no watch.
- Watch required checks on the draft PR. Accept
skippedorneutralonly for optional checks. - Use
fix-cifor related failures, with at most three diagnose/fix/push cycles. - Re-run an apparently unrelated failure once. If it fails again, report it and stop without changing unrelated code.
- When required draft checks pass, mark the PR Ready for review.
- Continue watching checks triggered by that transition under the same rules.
- Finish only when all required checks are green, or when a guardrail stops the workflow.
7. Restore the workspace
On success or early stop, preserve any removal work on its branch or a recovery stash, then return to the initial branch/ref and restore the saved stash so the workspace matches its starting state. Never discard work. If restoration conflicts, stop and report the conflict without resolving unrelated user changes.
© LedgerHQ, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (scripts) in .agents/skills/remove-feature-flag of LedgerHQ/ledger-live.
- SKILL.md
- scripts/read-production-flag.mjs
- scripts/read-production-flag.test.mjs
Open the folder on GitHubat commit a3861a2
Compare with similar skills
Remove Feature Flag next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Remove Feature Flag this skillLedgerHQ/ledger-live | 621 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Management Talkthananon/9arm-skills | 3.2k | — | ~3.2k | Automated safety check: Pass | None | |
| YugabyteDB Issue Creatoryugabyte/yugabyte-db | 11k | — | ~2k | Automated safety check: Pass | Custom licence | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Code Reviewcroffasia/itsaplan | 895 | — | ~2k | Automated safety check: Pass | AGPL-3.0 | |
| Connect Apps with ComposioComposioHQ/awesome-claude-skills | 77k | 3 repos | ~557 | Automated safety check: Pass | None |
Similar skills
YugabyteDB Issue Creator
yugabyte/yugabyte-db
Creates a GitHub issue or JIRA ticket for a YugabyteDB change or bug, after scrubbing customer data, secrets and unreleased details from anything public.
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Code Review
croffasia/itsaplan
A skill your agent uses when reviewing code — a diff, a merge request, a file, a directory, or a feature.
Connect Apps with Composio
ComposioHQ/awesome-claude-skills
Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.
Git Worktree Setup
k8zdev/k8z
Automate git worktree creation and copy private files (not tracked in git) to new workdirs.
More from LedgerHQ/ledger-live
All 50 skills in this repoImpacting PRs
LedgerHQ/ledger-live
Find which open PRs are impacted by a migration/sunset/refactor and notify their authors — blocking review when the old path is already gone from develop, heads-up comment when it is only deprecated…
Cloud Sync Module
LedgerHQ/ledger-live
Write, review or debug a cloudSyncModule.ts — a CloudSyncDataManager that syncs one slice of user data through Ledger Sync (Cloud Sync).
Codeownership
LedgerHQ/ledger-live
Maintain CODEOWNERS file and team directories. An agent skill from LedgerHQ/ledger-live.
Coin Families Contract
LedgerHQ/ledger-live
Coin-specific families logic must live in families/. An agent skill from LedgerHQ/ledger-live.
Data Layer Advanced
LedgerHQ/ledger-live
Structure a Ledger Wallet data layer where one API response serves several entities.
Debug Rn Native Crash
LedgerHQ/ledger-live
Investigate native React Native crashes (Fabric/Hermes/iOS) in ledger-live-mobile when JS error logs are missing or unhelpful.
Related
Questions about Remove Feature Flag
What does Remove Feature Flag do?
Remove a Ledger Wallet feature flag while preserving its resolved production behavior, then validate, create a draft PR, and watch CI to green. Remove Feature Flag is an agent skill from LedgerHQ/ledger-live. Remove a Ledger Wallet feature flag while preserving its resolved production behavior, then validate, create a draft PR, and watch CI to green.
How do I install Remove Feature Flag in Claude Code?
Run `npx skills add LedgerHQ/ledger-live --skill remove-feature-flag -a claude-code`. Or copy the skill folder (.agents/skills/remove-feature-flag in LedgerHQ/ledger-live) into .claude/skills/remove-feature-flag in your project. Claude Code loads it when a task matches its description.
How do I install Remove Feature Flag in Codex?
Run `npx skills add LedgerHQ/ledger-live --skill remove-feature-flag -a codex`. Or copy the skill folder (.agents/skills/remove-feature-flag in LedgerHQ/ledger-live) into .agents/skills/remove-feature-flag in your project. Codex loads it when a task matches its description.
Can I use Remove Feature Flag in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LedgerHQ/ledger-live --skill remove-feature-flag -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/remove-feature-flag, .gemini/skills/remove-feature-flag, .github/skills/remove-feature-flag and .opencode/skills/remove-feature-flag in your project.
What does Remove Feature Flag need to run?
Going by SKILL.md and its folder, Remove Feature Flag needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js.
Does Remove Feature Flag access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Remove Feature Flag safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Remove Feature Flag use?
Remove Feature Flag is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Remove Feature Flag use?
About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Remove Feature Flag?
Skills that share tags, products or a category with Remove Feature Flag: Management Talk (thananon/9arm-skills, 3.2k stars), YugabyteDB Issue Creator (yugabyte/yugabyte-db, 11k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars) and Code Review (croffasia/itsaplan, 895 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Remove Feature Flag?
LedgerHQ (a GitHub organization) maintains it in LedgerHQ/ledger-live, which has 621 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 7, 2026.
Source: LedgerHQ/ledger-live on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.