popoffvg/context-save
harness/plugins/memory-keeper/skills/context-save/SKILL.md
This skill should be used when the user says "context save", "remember this", "save this", "note this for later", "keep this", or wants to persist any knowledge, pattern, decision, or learning from the current session to persistent memory.
$ install --global
skillsauthnpx skillsauth add popoffvg/dotfiles context-saveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 20, 2026, 4:46 AM386.5s1 file scanned
SKILL.md
- name:
- context-save
- description:
- This skill should be used when the user says "context save", "remember this", "save this", "note this for later", "keep this", or wants to persist any knowledge, pattern, decision, or learning from the current session to persistent memory.
Context Save
Usage
/context save <what to remember>
Configuration
Read insights_root from ~/.claude/memory-keeper.local.md YAML frontmatter. If the file is missing, stop and ask the user to create it.
Classifications
| Classification | What it is | Saved to |
|---|---|---|
| insight | Completed work — architecture, patterns, gotchas, decisions | <insights_root>/<repo>/insights.md |
| agent_edit | AI behavior changes — hooks, prompts, skills, CLAUDE.md, plugin config | <insights_root>/claude-config/behavior.md |
| none | Routine work, nothing worth recording — skip silently |
One save invocation may produce multiple entries with different classifications.
Entry Format
## <Keyword-rich title, 3-7 words> — YYYY-MM-DD HH:MM
<Lead: direct statement of what this is and why it matters. 1-3 sentences.
Include concrete identifiers: file paths, function names, config keys, env vars.
No preamble — write for someone with zero memory of this session.>
### Subsection (only when topic has multiple distinct aspects)
<Details>
Heading rules — the heading is the search key:
- Include the main entity + key relationship
- Must be findable by someone who forgot: "what was that thing about X?"
- Good:
Pi session_shutdown: handler awaited before process.exit - Good:
RocksDB WAL mode: disable for unit test performance - Good:
Claude Code Stop hook fires per-turn not per-session - Bad:
Shutdown analysis,Important fix,Database stuff
Body rules:
- Lead sentence must be self-contained — complete picture without reading more
- Never start with "In this session...", "We discovered...", "It was found..."
- State facts directly: "X does Y because Z"
- Subsections only for 2+ distinct concerns within the same topic
Good entry:
## Pi session_shutdown: handler fully awaited — 2026-03-19 10:00
Pi's `shutdown()` in `interactive-mode.js` calls `await extensionRunner.emit("session_shutdown")`
before `process.exit(0)` — handlers have unlimited time. The current fire-and-forget
`processAllPending().catch()` call is a bug: it escapes the await chain and gets killed.
Fix: either `await processAllPending()` directly, or spawn a detached child process.
Bad entry (skip these):
## Shutdown fix — 2026-03-19
- Fixed the shutdown issue
- Added await
Repo Detection
Run git -C <cwd> rev-parse --show-toplevel 2>/dev/null | xargs basename. Fallback: basename <cwd>. User or conversation context may override.
Deduplication
Before appending, read the target file and check:
- Exact heading match → skip
- Semantic overlap → skip (same fact, different words)
- New entry is broader → replace old entry
- Existing entry is broader → skip
One precise entry beats two fuzzy ones.
Related Skills
popoffvg/improve-claude-local
tools
VerifiedTrustedCommunity
Improve a whole CLAUDE.local.md — the private, per-project rules captured from user corrections. Wraps each conditional rule in a <task-relevant> block so it only surfaces for matching work, merges duplicates, generalizes one-off facts, drops stale entries, and routes raw project facts to engram. Use when the user says "improve claude.local", "clean up the local rules", "claude.local is bloated", or after the Stop hook has appended many rules.
2SKILL.mdUpdated Jun 25, 2026
popoffvg/workflow
testing
VerifiedTrustedCommunity
WM pipeline and conventions shared across all phases. Agents must read this before spec, impl, or verify work.
2SKILL.mdUpdated Jun 19, 2026
popoffvg/code
development
VerifiedTrustedCommunity
One entry point for spec writing, implementation, and bug fixing. Default is new (write spec → grill loop → produce notes → author TODO bodies). Other subcommands: verify (audit), revise (sync to shipped), prototype (settle a decision), code-map (diagram), impl (execute one TODO), fix (analyze cause, correct thoughts, fix behavior), help (this page). Invoke as /code <subcommand>.
2SKILL.mdUpdated Jun 19, 2026
popoffvg/red-green-refactor
development
VerifiedTrustedCommunity
Red-Green-Refactor cycle for bug fixes. Before fixing a bug, first write a failing test that reproduces it (Red), then make the minimal change to pass (Green), then clean up the code (Refactor). Use on any bug fix, error correction, failing test repair, or when user says "fix this bug".
2SKILL.mdUpdated Jun 18, 2026