← ClaudeAtlas

fi-archivelisted

Move old [fixed] entries out of docs/found-issues.md into docs/found-issues-archive.md (keeps the newest 50 or 30 days, whichever threshold hits first). Mutating and one-way — the archive file is append-only and entries do not come back, so use --dry-run to preview. Open and deferred entries are never touched. Use when the [fixed] tail is drowning the ledger, not as routine post-sync cleanup.
AltDoug/found-issues · ★ 1 · Code & Development · score 74
Install: claude install-skill AltDoug/found-issues
<!-- loc-override: generated 1:1 from commands/archive.md by scripts/gen-codex-skills.sh; length is owned by the source command file --> Run `found-issues archive <the user-provided arguments>` to move old `[fixed]` entries from the active `docs/found-issues.md` to `docs/found-issues-archive.md`. ## When to run this **Usually you don't need to.** Auto-archive runs after every `$fi-sync` by default, so old fixed entries get moved without you thinking about it. Run this command manually when you want to: - Use custom thresholds: `$fi-archive --days=14 --count=20` - Preview what's eligible: `$fi-archive --dry-run` - Force a one-time cleanup if you've disabled auto-archive Disable auto-archive with `export FOUND_ISSUES_AUTO_ARCHIVE=off` in your shell rc. The active file accumulates `[fixed]` entries as a closure record. Over time (especially during heavy work — 25+ entries/day is normal during active development), this can grow to hundreds of entries. The archive command keeps the active file focused on what's still actionable while preserving the closure history. ## Default behavior `$fi-archive` with no args: - Archives any `[fixed]` entry whose closure date (`(fixed: YYYY-MM-DD)`) is older than **30 days** - AND/OR archives the oldest `[fixed]` entries when the total exceeds **50** (oldest move first until count is back at threshold) - Entries are appended to `docs/found-issues-archive.md` (created on first run with a permanent header) - The archive file is appe