revisitlisted

Revisit dashboard — one scan of everything you parked to re-check later, across every skill's memory. Reads out/*/tracker.md and the other memory files skills leave behind (ideate PARK "revive when", verdict/scout revisit-when triggers, refactor WATCH candidates, learn spaced-repetition due dates, jobfit roles to re-check) and surfaces what's due now: date-based items past their date, trigger-based items whose condition may have fired. Renders one prioritized "due to re-check" list in chat — grouped by skill, most overdue first — quoting the exact tracker line and its revive trigger so you can act or defer. Strictly read-only: it never edits a tracker or fires the follow-up skill; it points, you decide. Use for "what do I need to revisit", "what's due to re-check", "anything parked worth reviving", "show my revisit queue" — e.g. "/revisit", "/revisit ideate".
duthaho/skillhub · ★ 6 · AI & Automation · score 75

Install: claude install-skill duthaho/skillhub

# revisit — what you parked, now due `/revisit` — scan every skill's memory for items due to re-check `/revisit <skill>` — only that skill's tracker (e.g. `/revisit ideate`) Skills that judge under uncertainty don't just decide — they record a **trigger for revisiting the decision**: ideate PARKs an idea "revive when X", verdict stamps "revisit-when", scout/refactor leave WATCH items, learn schedules the next review by date. Scattered across `out/*/`, those triggers rot unseen. This skill is the one place that gathers them and asks a single question: **what is due to re-check right now?** It is **strictly read-only** — the same contract as `daybrief`. It never edits a tracker, never marks anything revived, never runs the follow-up skill. It surfaces; you decide. ## Step 0 — Locate the memory Today's date is `date +%F` (compute it; don't hardcode). Then find `out/` in the current project. - No `out/`, or no memory files under it → say so plainly and stop. Nothing to revisit is a valid, complete answer (keyless, graceful — never invent items). - `/revisit <skill>` → restrict the scan to `out/<skill>/` only. **Completion criterion:** the set of memory files to scan is fixed, or a clean "nothing to revisit yet" is reported. ## Step 1 — Collect the revisit signals Read each memory file and pull every line carrying a revisit signal. Known shapes (don't limit to these — any "revive/revisit/recheck/due" marker counts): | Source | Signal to pull | |---|---| | `out/ideate/t