dino-cosic/flagrm / skills/flagrm-remove
flagrm-remove
VerifiedUse when the user asks to remove, retire, deprecate or clean up a feature flag or feature toggle, says a flag is fully rolled out, or runs /flagrm-remove <flag>, in a repository with a flagrm.config.yaml. Works for Angular, .NET and other stacks: IFeatureManager, [FeatureGate], appsettings FeatureManagement, LaunchDarkly-style calls, flags objects, enums, signals, *ngIf/@if templates.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.0 KB |
| batch.md | markdown | 1.7 KB |
| patterns.md | markdown | 3.5 KB |
batch.md
View on GitHub# Remove several flags
Run SKILL.md's workflow once per flag, in the order given, one commit per flag.
Each baseline reuses the previous flag's passing verify (seconds) only if the commit leaves the tree as verified.
## Once, before the first flag
1. SKILL.md step 1 preconditions. Find every flag in `flagrm list --json`; for one that's missing, show the closest names and ask.
2. One table: flag, `state`, and for any not `on` the environments in `config[]` that change.
`unconfigured` flags follow SKILL.md's `flagrm stale` rule. Ask once about the rest: "Remove all of these as ON everywhere?" On a no, drop the flags the user names.
3. Ask once: "Commit each flag once its verify passes?"
## Per flag
Copy this checklist for each flag and tick it as you go:
```
<flag>:
- [ ] baseline (step 2)
- [ ] every usage found (step 3)
- [ ] removed (step 4)
- [ ] verify passes (step 5)
- [ ] handed back (step 6)
- [ ] committed
```
- The ON answer above is step 1's state answer: don't ask again.
- Commit answer yes: commit with the proposed message, then start the next flag. No: show the message,
stop, and continue once the user says it's committed. The next baseline needs the previous removal committed.
- A flag that needs the user (three failed attempts on one check, an unclear case) pauses the batch.
Never start a flag while the previous one is uncommitted.
- Optional: if you can start subagents, run each flag in its own, one at a time. A subagent sees no
conversation history: give it the flag, that it is confirmed ON everywhere, the commit answer, and
"follow flagrm-remove's SKILL.md steps 2–6".
## At the end
One table: flag, commit, remaining warnings, kept on purpose.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |