catchup
Scannednpx machina-cli add skill eidetics/claude-eidetic/catchup --openclaw/catchup
Step 1: Detect Project
PROJECT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
if [ -n "$PROJECT_ROOT" ]; then
PROJECT_NAME=$(basename "$PROJECT_ROOT")
NOTES_DIR="$HOME/.eidetic/notes/$PROJECT_NAME"
echo "PROJECT_NAME=$PROJECT_NAME"
echo "NOTES_DIR=$NOTES_DIR"
echo "EXISTS=$([ -d "$NOTES_DIR" ] && echo yes || echo no)"
echo "FILE_COUNT=$([ -d "$NOTES_DIR" ] && ls "$NOTES_DIR"/*.md 2>/dev/null | wc -l || echo 0)"
else
echo "NO_GIT_REPO"
fi
- Argument overrides PROJECT_NAME (e.g.
/catchup myproject). - If NO_GIT_REPO and no argument, ask for project name.
- If EXISTS=no or FILE_COUNT=0: "No session notes for <PROJECT_NAME>. Run /wrapup to enable recovery." Stop.
Step 2: Refresh Index
index_codebase(path="<NOTES_DIR>")
Step 3: Search
search_code(path="<NOTES_DIR>", query="recent decisions and changes for <PROJECT_NAME>", limit=5)
search_code(path="<NOTES_DIR>", query="open questions next actions blockers", limit=5)
Step 4: Read Top Notes
Collect unique file paths, sort by filename date descending, read top 2-3 in full.
Step 5: Present Summary
## Catchup: <PROJECT_NAME>
**Last session:** <date> | **Status:** <1-line status>
- <Key decision or change>
- <Critical open question>
- <Next action>
**Open items:** <N> | **Notes:** <N> files, <date range>
Expand only if user asks.
Fallback
If Eidetic fails, read the 3 most recent files directly:
ls -t "$NOTES_DIR"/*.md 2>/dev/null | head -3
Source
git clone https://github.com/eidetics/claude-eidetic/blob/main/plugin/plugins/claude-eidetic/skills/catchup/SKILL.mdView on GitHub Overview
catchup reconstructs project context by locating Eidetic-searchable notes, indexing the project’s notes directory, and surfacing recent decisions, open questions, and next actions. It guides you through detecting the project, refreshing the index, searching for key items, and presenting a concise summary of the last session.
How This Skill Works
The skill detects the current Git project to determine the project name and notes directory. It then refreshes the Eidetic index for that directory, runs targeted searches for recent decisions and open items, reads the top 2–3 notes in full, and presents a structured summary. If Eidetic fails, it falls back to listing the three most recent notes directly from the notes directory.
When to Use It
- You return after a break and need to recover the latest project context.
- You’re starting a new project and want a quick, accurate catch-up of decisions and next actions.
- You want to recall decisions and blockers after a sprint review or team meeting.
- You are onboarding a new teammate and need a succinct project recap.
- Eidetic retrieval stalls or fails and you need a fallback view of recent notes.
Quick Start
- Step 1: Detect Project (run /catchup <PROJECT_NAME> or rely on the current Git repo).
- Step 2: Refresh Index (index_codebase(path="<NOTES_DIR>")).
- Step 3: Search and Read Top Notes, then Present Summary (see Step 3–5 in SKILL).
Best Practices
- Always run in the project’s Git repository to ensure PROJECT_NAME is detected correctly.
- Keep notes organized under ~/.eidetic/notes/PROJECT_NAME for reliable indexing.
- Run the index step after project detection before performing searches.
- Use the queries for decisions/changes and for open questions/next actions to surface relevant items.
- Read the top 2–3 notes in full to ground the summary before presenting it to teammates.
Example Use Cases
- After a two-week hiatus on Project Atlas, catchup surfaces the latest decisions and next steps.
- Onboarding a new developer to Project Helix with a fast, accurate recap of recent work.
- Between sprints, you quickly reconstruct status from recent Eidetic notes.
- Cross-team handoff—summarize decisions and blockers for a smooth transition.
- Reactivating a paused feature by reviewing the latest notes and upcoming actions.
