Agent skill · shipshitdev
recall
Rebuild recent working context from chat history, live state, and the shared record, then hand back a tight current-state brief. Use for recall my work on X, catch me up, what have I been working on, or where did I leave off.
What it needs
About 2k tokens when loaded.
What this skill does
Recall Before you start or resume work, rebuild the user's recent working context and hand back a tight capsule. Companion to pstack Session pickup (one specific prior chat) and memory-systems (designing persistent agent memory). This skill loads working context across recent chats and the shared record. Authorized Scope Apply this engine only within the user's requested task and existing explicit authorization. Loading or delegating to it grants no additional authority. Preserve report-only restrictions and the caller's target, host, provider, and cost limits. Existing approval satisfies a gate only for the same actions and scope; obtain approval before expanding them. Forward these limits to delegates. Contract Inputs: An optional topic and time window (default last 7 days) The active workspace only Outputs: A brief: capsule, tagged threads, recurring problems, next move Creates/Modifies: None External Side Effects: Read-only git / gh and whatever evidence connectors why uses Confirmation Required: None Delegates To: why investigators for the shared record Recommend pstack Session pickup when the ask is one specific prior chat Steps 1. Classify. One specific prior chat is Session pickup. A full state capsule already in the message skips mining. 2. Lock the scope. Pin the window, the topic, and the workspace. State the scope back. Never quietly turn "all" into "recent N". Never read another project's transcripts without being asked. 3. Fan out across chat history. Spawn parallel subagents on the fast cheap tier. Order candidates by real modification time. Each returns topic, goal, decisions, open threads, struggles, and artifacts, citing the chat id the harness uses. 4. Sweep the shared record whenever the topic names a feature, file, subsystem, or bug. Hand it to why investigators, steered to current state, what was tried, and what users still report. 5. Verify against live state with git and gh. 6. Write the brief to the contract below. Output contract Capsule. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills shipshitdev/recall