Menu
Save current session context to native memory plus omx-memory or AgentMemory-compatible backends
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
6-stage structured development cycle with stage-based tool restrictions
Multi-angle release quality verification using parallel expert review teams
Full Self Driving — autonomous release loop that processes all auto-dev-eligible GitHub issues until none remain, by repeatedly running /pipeline auto-dev then /homework.
Invoke and resume YAML-defined pipelines by name — /pipeline auto-dev runs the full release pipeline
Analyze release workflow findings and recommend follow-up actions — execute immediately or register as issues
Auto-detect project context and optimize harness — deactivate unused agents/skills, suggest missing experts, generate project profile
| name | memory-save |
| description | Save current session context to native memory plus omx-memory or AgentMemory-compatible backends |
| scope | core |
| argument-hint | [--tags <tags>] [--include-code] |
| disable-model-invocation | false |
| user-invocable | true |
Save current session context to native memory and the configured searchable MCP backend for persistence across context compaction. Prefer omx-memory or AgentMemory-compatible tools (memory_add, observation_add). Deprecated Chroma memory backends are not used in this project.
--tags, -t Additional tags for the memory
--include-code Include code changes in the save
--summary, -s Custom summary (otherwise auto-generated)
--verbose, -v Show detailed save information
1. Collect session context
├── Tasks completed
├── Decisions made
├── Open items
└── Code changes (if --include-code)
2. Format with metadata
├── project: my-project
├── session: {date}-{uuid}
├── tags: [session, ...user_tags]
└── created_at: {timestamp}
3. Store in configured backend
├── Prefer memory_add for summaries
├── Prefer observation_add for atomic learnings
└── Skip searchable save when no approved backend is configured
4. Report result
project: my-project
session: {date}-{uuid}
tags: [session, task, decision]
content:
summary: Brief description of session context
tasks_completed: List of completed tasks
decisions: Key decisions made
open_items: Unfinished work
[sys-memory-keeper:save]
Saving session context...
Context collected:
Tasks: 3 completed
Decisions: 2 recorded
Open items: 1 pending
Metadata:
Project: my-project
Session: 2025-01-24-a1b2c3d4
Tags: [session, task, decision]
[Done] Session context saved successfully.
Memory ID: mem_abc123
[sys-memory-keeper:save --tags "authentication,oauth"]
Saving session context...
Metadata:
Project: my-project
Session: 2025-01-24-a1b2c3d4
Tags: [session, task, decision, authentication, oauth]
[Done] Session context saved successfully.
Memory ID: mem_abc123
[sys-memory-keeper:save --verbose]
Collecting session context...
Tasks Completed:
1. Implemented OAuth flow
2. Added JWT token validation
3. Created authentication middleware
Decisions Made:
1. Use RS256 for JWT signing
Rationale: Better security for distributed systems
2. Token expiry: 1 hour
Rationale: Balance security and user experience
Open Items:
1. Refresh token implementation
Status: In progress
Saving to configured memory backend...
Document content:
## Session Summary
Date: 2025-01-24
...
[Done] Session context saved.
Memory ID: mem_abc123