recall
/recall
Składa krótki opis bieżącej pracy z historii czatu, stanu na żywo i wspólnych zgłoszeń, zanim zadanie zostanie wznowione.
- Autor
- painhardcore ↗
- Repozytorium
- pstack ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Składa krótki opis bieżącej pracy z historii czatu, stanu na żywo i wspólnych zgłoszeń, zanim zadanie zostanie wznowione.
Wyzwalacze z opisu
Oryginalny opis (EN)
Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.
Jak działa
- Output contract
Podgląd SKILL.md
---
name: recall
description: "Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work."
---
# Recall
**Before you start or resume work, you rebuild the user's recent working context and hand back a tight capsule of where things stand now and what to do next.**
Keep it tight and on-topic. Read only what the in-scope threads need, then stop.
Your context lives in two records. Your own chat history holds what you did and decided. The shared record holds everything that happened around the same code under other names: the symptoms users keep reporting, the fixes that shipped and got reverted, the errors still firing in prod. That second record is what the **why** skill searches, across source control, the issue tracker, chat and issue channels, long-form docs, and error tracking. A feature with a long bug tail keeps most of its story there, so don't reconstruct it from your transcripts alone.
Use the active host's thread history, transcript API, or current-session context. Do not guess private filesystem paths or scan unrelated projects. If the host exposes no prior history, reconstruct from the repository and the context the user supplied.
1. Classify, then route. One specific prior chat to resume is the `session-pickup` playbook, not this. A human-readable summary of your work is a different task. Recall loads working context across recent chats before you act. If the user already gave you a full state capsule (paths, branch, the change), use it and skip the mining.
2. Lock the scope before searching. Pin the window ("recent" is a real range, default the last 7 days), the topic if named, and the workspace (default the active one. Never read another project's transcripts without being asked). State the scope back. Never quietly turn "all" into "recent N".
3. Search the available chat history. When subagents are available and permitted, give each one a disjoint time slice. Otherwise search inline. Order candidates by real modification time, search the topic first, read only matching regions, and skip the current chat plus obvious subagent, eval, and test noise. Return one block per chat with the topic, user goal, decisions, open threads, corrections, and artifacts. Cite the host's stable task or chat identifier when one exists. For one or two chats, skip the fan-out and search directly. The raw transcripts stay in the subagents. The main thread gets only their findings. Pick each subagent's reasoning level for the job, per the Subagents section of the **poteto-mode** skill.
4. Sweep the shared record whenever the topic names a feature, file, subsystem, area, or bug. This is the default, not a judgment call, and "my work on X" does not exempt it. Hand it to the **why** skill's source investigators, but steer their question from "why was this built this way" to "what's the current state, what's been tried and didn't hold, and what are users still reporting". Reuse its per-source playbooks, run the investigators in parallel with the chat-history mining, and inherit its posture: one investigator per source, null results are findings, skip an unavailable MCP and say so. Fold what comes back into the brief. Skip this step only for pure activity recall with no named target ("what did I do this week"), where your own history and live state are the entire answer.
5. Verify against live state. Take the PRs, branches, and tickets that the mining and the sweep surfaced and check them with `git` and `gh`. When the answer hinges on what an agent actually did (the tools it ran, files it read, errors it hit), read the full transcript, not just a trimmed local copy.
6. Write the brief to the contract below. Group by thread. Stay on the named topic.
## Output contract
Lead with the capsule, then the thread status, then the problems, then the next move. Deeper detail goes below or gets cut.
- **Capsule.** At most 5 bullets. What this work is and where it stands overall.
- **Threads.** One line each, prefixed with exactly one status tag: `[merged #N]`, `[open PR #N]`, `[in flight <branch>]`, `[verified, uncommitted]`, `[reverted #N]`, or `[planned, not started]`. A thread with no tag is not done yet, so tag it.
- **Problems.** At most 5, the recurring ones. Include the symptoms users keep reporting and any fix that shipped and was reverted, so the next attempt starts where the last one failed.
- **Next move.** The single most useful next action, concrete.
An adjacent feature or ticket stays out unless it blocks this one. When the capsule and thread lines outgrow a screen, cut detail before you cut threads. Write the brief through the **unslop** skill, cite chat findings by UUID and shared-record findings by their source (PR #, ticket ID, chat permalink, error-tracker issue), and sanitize private context before any public output.
**Reply:** the brief, to the contract above.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · painhardcore/pstack | 90 | MIT |
| gtapps/hermitd | 100 | MIT |
| wenlan-app/wenlan | 100 | Apache-2.0 |
| wenlan-app/wenlan | 100 | Apache-2.0 |
| davepoon/buildwithclaude | 100 | MIT |
| rohitg00/agentmemory | 100 | Apache-2.0 |
| smart-ai-memory/attune-ai | 100 | Apache-2.0 |
| spencerneutron/Synapse | 100 | MIT |
| cihanatak/lr-memory | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki f5c0fddd788d (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100spirit-world
Odzyskuje kontekst ostatniej pracy z historii czatów Claude Code i Codexa, stanu gita i PR-ów oraz wspólnego zapisu przed wznowieniem. - 90thinkweave-recall
Przywołuje wcześniejsze decyzje i kontekst z ThinkWeave tylko do odczytu, na wyraźne polecenie użytkownika. - 100obsidian-brief
Syntetyzuje brief kontekstowy z ostatnich logów sesji i zapisów w Obsidianie dla bieżącego projektu na początku pracy, w trybie odczytu. - 95slm-recall
Wyszukuje fakty, decyzje i wcześniejszy kontekst w SuperLocalMemory, zanim cokolwiek nowego zostanie zapisane. - 100mora-recall
Pobiera historię użytkownika o osobach, projektach, spotkaniach, wiadomościach, decyzjach i zobowiązaniach, zanim odpowie na pytania o przeszłą pracę.