Run the quarterly feature-flag cleanup workflow on the current repo
73%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.gemini/skills/flag-cleanup/SKILL.mdRun the full feature-flag cleanup workflow:
/flag-cleanup
/flag-cleanup --max-age-days 60
/flag-cleanup --flag-doc runbooks/flags.mdThis command dispatches to the feature-flags-architect skill:
SKILL=engineering/feature-flags-architect/skills/feature-flags-architect
# Step 1: scan for debt
python "$SKILL/scripts/flag_debt_scanner.py" --repo . --max-age-days "${MAX_AGE_DAYS:-90}" --format json > .flag-debt.json
# Step 2: audit kill switches
python "$SKILL/scripts/kill_switch_audit.py" --repo . --flag-doc "${FLAG_DOC:-docs/feature-flags.md}" --format json > .kill-switch-audit.json
# Step 3: synthesize a markdown report
# (Claude reads both JSON files, groups by owner, drafts the cleanup plan)A markdown report with:
docs/feature-flags.md)feature-flags-architect skill is installed.flag-debt.json and .kill-switch-audit.json written to repo root (ignored via .gitignore)alirezarezvani/claude-skills
f8593c4
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.