From kagura-memory
Save session knowledge to Kagura Memory Cloud before ending a conversation
npx claudepluginhub kagura-ai/memory-cloud --plugin kagura-memorySummarize the current session's key learnings and save them to Kagura Memory Cloud. ## When to use At the end of a development session, or when switching to a different task. Captures decisions, patterns, bugs, and plans that would be useful in future sessions. ## Steps ### 1. Identify related GitHub issues Review the conversation and collect all GitHub issue numbers that were worked on, referenced, or discussed. Use `gh issue view <number>` if needed to confirm titles. ### 2. Identify what to remember Review the conversation and categorize knowledge into: | Type | What to capture |...
/session-summaryCreate a structured summary of the current conversation and save it to sessions/
/session-summaryBu session'da yapilanlari ozetle ve `.claude/tmp/session-[tarih].md` dosyasina kaydet.
/session-summaryGenerate a comprehensive session summary document with accurate timestamps and metadata.
Summarize the current session's key learnings and save them to Kagura Memory Cloud.
At the end of a development session, or when switching to a different task. Captures decisions, patterns, bugs, and plans that would be useful in future sessions.
Review the conversation and collect all GitHub issue numbers that were worked on, referenced, or discussed. Use gh issue view <number> if needed to confirm titles.
Review the conversation and categorize knowledge into:
| Type | What to capture | Importance |
|---|---|---|
decision | Architecture decisions, approach choices, rejected alternatives with WHY | 0.8-1.0 |
pattern | Implementation patterns, technical solutions, reusable approaches | 0.7-0.9 |
bug-fix | Root cause analysis, regression lessons, "never do this again" | 0.8-0.9 |
note | Milestone status, roadmap changes, issue relationships | 0.6-0.8 |
learning | SDK benchmark results, performance findings, tool limitations | 0.6-0.8 |
troubleshooting | Error solutions, workarounds, environment-specific fixes | 0.5-0.7 |
list_contexts()
Ask the user which context to save to if unclear. Default: the project's development context.
For each item, use remember with:
category:{domain} + entity tags + writing variations for Japanese + issue:#N for each related issueRelated issues: #N, #M line at the end of content linking to relevant GitHub issues.["vault://my-vault/related-note.md"]). Unresolved URIs are silently skipped.type="troubleshooting" with tags=["dev-environment"] so future sessions can avoid the same mistakeAfter saving, print a summary:
## Session Knowledge Saved
Related issues: #12, #34
| # | Type | Summary | Importance |
|---|------|---------|------------|
| 1 | decision | ... | 0.9 |
| 2 | pattern | ... | 0.8 |
...
Total: N items saved to context {context_name}