Stats
Actions
Tags
From vector-memory
Loads project context from git history, waypoint snapshots, and vector memories. Checks staleness, searches architecture memories, and presents commits, state, next steps for resuming work.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vector-memory:waypoint-getThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Load context for current project using vector-memory.
Load context for current project using vector-memory.
git log --oneline -10 2>/dev/null
git branch --show-current 2>/dev/null
Call mcp__vector-memory__get_waypoint to retrieve the latest waypoint snapshot.
After reading waypoint, check for staleness:
git log --oneline --since="[waypoint date]" 2>/dev/null
If commits exist after waypoint: Show them, ask user whether to use waypoint or skip it.
If no waypoint exists: Note it and continue to step 3.
Call mcp__vector-memory__search_memories with:
If the waypoint includes memory IDs, call mcp__vector-memory__get_memories with those IDs to retrieve full context.
# Context: [Project]
**Dir:** [path] | **Branch:** [branch] | **Waypoint:** [date or None]
## Git Activity
[recent commits]
## State
[from waypoint summary, completed items, blockers]
## Next Steps
[from waypoint next_steps]
## Relevant Memories
[key memories from search + referenced memories]
Combine waypoint document with retrieved memories to establish full context. Then:
No waypoint / no memories: Just note it and ask what we're working on.
npx claudepluginhub aeriondyseti/vector-memory-mcp --plugin vector-memoryRecalls project context via ctx CLI: loads context packet, reads TASKS.md/DECISIONS.md, lists recent sessions, presents structured readback of last session, active tasks, recent decisions, next steps. For memory questions or session starts.
Rebuild context on a project's current state using git diffs, checkpoints, annotations, and prior conversation search.
Maintains a living STATE.md document tracking current project context, active tasks, blockers, and next steps. Auto-loads at session start or on explicit commands like 'update state' or 'where was I'.