← ClaudeAtlas

review-resurfacelisted

Surface dormant reviewer-feedback notes from tasks/reviews/ (and _archive/) whose applies_to topics match the current task, returning POINTERS ONLY — paths plus frontmatter, never bodies. Recovers a past reviewer rule relevant to the work at hand without bloating Tier-1 boot. Delegates the deterministic scan and scoring to scripts/review-resurface.sh.
tansuasici/claude-research-kit · ★ 0 · Code & Development · score 75
Install: claude install-skill tansuasici/claude-research-kit
# Review Resurface ## Core Rule The kit's compounding memory lives in `tasks/reviews/` — every correction from the author or a referee, as a note (`CLAUDE.md → Self-Improvement Loop`). But only the highest-leverage handful are promoted to `_index.md → ## Top Rules` and read at every session boot. The rest go **dormant**: still true, still worth obeying, but not in context — and rightly so, because loading every review at boot would bloat Tier 1 and drown the active task. `/review-resurface` recovers exactly the dormant rules that match what you are about to do. You are revising the Discussion; somewhere in `tasks/reviews/` is the note "you keep overclaiming in the discussion" that never made Top Rules — this surfaces it, *now*, when it is about to bite, and stays silent the rest of the time. The contract is **pointers only**: paths plus frontmatter (`applies_to`, `title`, `date`), **never the bodies**. The skill tells you a relevant rule *exists and where*; **you** decide which to Read. This is deliberate — pulling N full review bodies into context to find the one that matters defeats the purpose. The agent reads selectively; the scan does not pre-load. ## When to Use Invoke with `/review-resurface "<task summary>"` when: - Starting work on a section a reviewer has historically flagged — before drafting, recover the rule so you do not re-earn the critique. - A `/retro` is scanning recurring critiques and wants the dormant notes relevant to the upcoming focus. - After a