recall
Reconstruct recent work on a named project or topic from scoped agent sessions and current project evidence. Use for catch-me-up and where-did-I-leave-off requests.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- recall
- metadata
- { "author": "Brenden Bishop", "attribution": "../../ATTRIBUTION.md" }
- description
- Reconstruct recent work on a named project or topic from scoped agent sessions and current project evidence. Use for catch-me-up and where-did-I-leave-off requests.
03 SKILL.md 正文
Recall
Give the user a current, compact account of their work. Start with the project and topic they named. Default to the active project and the last seven days if they gave no scope. Use the session reader to list recent sessions, then open only relevant ones. Do not search unrelated projects. For Amp, confirm the thread belongs to this project and time window before reading it and pass --allow-unverified-amp; its list output does not establish either match.
Combine session findings with live Git, PR, ticket, or workspace state when available. A transcript records what an agent reported then; it does not prove what is true now. Cite a session ID or artifact for consequential facts. If the request is to resume one identified chat or handoff, use session-pickup or handoff instead of mining a wider history. If the user already supplied enough context, skip the crawl.
Reply with where things stand, what remains unresolved, and the most useful next move. Name coverage gaps briefly. Recall is read-only and does not create durable memory.
04 同仓库更多 Skills
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
unslop
Cut AI tells from any writing. Must always apply.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.