revisit

Scans skill memory files and identifies items due for revisit or re-check.

8|1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/duthaho/skillhub --skill revisit-duthaho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revisit
Source: https://github.com/duthaho/skillhub/tree/main/.claude/skills/revisit
Command: npx skills add https://github.com/duthaho/skillhub --skill revisit-duthaho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gathers all the things you previously parked for later and tells you which ones are due to be checked again now, so overdue follow-ups do not get lost across different skill memories.

Core Features & Use Cases

  • Scans memory files across skills for revisit signals such as revive dates, revisit-when triggers, WATCH items, and spaced-repetition review dates.
  • Separates items into due now versus not yet due, with the exact tracker line and trigger preserved for review.
  • Use it when you want a single prioritized queue of what to revisit across ideate, verdict, scout, refactor, learn, and jobfit memories.

Quick Start

Ask the skill to scan your workspace for anything due to revisit now and show the prioritized queue.

Frequently Asked Questions about revisit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find spaced repetition notes and watchlist items that are due for a revisit?

To find spaced repetition notes and watchlist items due for a revisit, scan existing memory files to classify open items by date or trigger. This surfaces a prioritized queue separating items due now from those not yet due, preserving exact tracker lines for review.

What is the best way to consolidate overdue follow-ups from multiple workspace trackers?

The best way to consolidate overdue follow-ups is to scan memory files across different skills for revisit signals like revive dates or WATCH items. This creates a single prioritized queue of overdue tasks, preventing parked ideas or deferred roles from getting lost.

Can I use revisit to check trigger dates across ideate and jobfit memories without modifying state?

Yes, you can check trigger dates across ideate and jobfit memories without modifying state. The process reads existing memory files and classifies each open item by date or trigger, strictly preserving the exact tracker line and trigger for review without altering any data.

Does this approach work with spaced-repetition review dates and verdict triggers?

Yes, this approach works with spaced-repetition review dates and verdict triggers. It applies to workspace trackers, parked ideas, watch lists, and roles deferred for later review, scanning memory files to accurately identify which specific items are due for a re-check.