claude-skills__.gemini__skills__flag-cleanup
Run the quarterly feature-flag cleanup workflow on the current repo
- License 许可
- MIT
- 所属仓库
- agisota/old-one
- 最近更新
- 2026-07-04
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- description
- Run the quarterly feature-flag cleanup workflow on the current repo
03 SKILL.md 正文
/flag-cleanup
Run the full feature-flag cleanup workflow:
- Scan for stale flags (older than 90 days, used in ≤2 places)
- For each candidate, identify the introducing PR/issue and current owner
- Generate a removal plan grouped by owner
- Run kill-switch audit against the flag-doc registry
- Output a markdown report ready to share with the team
Usage
/flag-cleanup
/flag-cleanup --max-age-days 60
/flag-cleanup --flag-doc runbooks/flags.md
Implementation
This 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)
Output
A markdown report with:
- Stale flag candidates grouped by owner, with introducing commit links
- Undocumented flags that fail the kill-switch audit
- Incomplete documentation (missing fields per flag)
- Suggested removal PRs — one per owner
Pre-conditions
- Run from a git repository with the source code committed
- A flag-doc registry exists (default:
docs/feature-flags.md) - The
feature-flags-architectskill is installed
Post-conditions
.flag-debt.jsonand.kill-switch-audit.jsonwritten to repo root (ignored via.gitignore)- Markdown report streamed to terminal
- Recommended next step printed (which removal PR to start with)
04 同仓库更多 Skills
zoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
zeroize-audit
Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.
yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
yara-rule-authoring
Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.
x-twitter-growth
X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.
x-api
X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.