memory
Memory Skill
You have access to a long-term memory system. Use it to remember important facts across sessions.
When to Store Facts
After completing a task or learning something important about the project, store durable facts using memory.store_extraction. Look for:
- Tech stack: databases, frameworks, languages, platforms
- Conventions: coding standards, naming patterns, preferences
- Decisions: architectural choices, design decisions
- Preferences: user preferences that should persist
How to Store Facts
Call the memory.store_extraction MCP tool with:
More from codenamev/claude_memory
improve
Incrementally implement feature improvements from docs/improvements.md with tests and atomic commits. Focuses on new functionality rather than refactoring.
2release
Prepare and publish a new gem release — bumps version across all required files, validates tests/linting/MCP server, commits, and creates the GitHub release. Use this skill when the user says "release", "publish a new version", "bump the version", "cut a release", "prepare for release", "ship it", or any variation of wanting to publish a new gem version. Also use when the user asks about the release process or what steps are needed to release.
2debug-memory
Diagnose ClaudeMemory installation and configuration issues. Use when memory tools fail or setup seems broken.
2setup-memory
Automatically install, configure, or upgrade ClaudeMemory
2quality-update
Incrementally implement code quality improvements from docs/quality_review.md with tests and atomic commits. Run after /review-for-quality to apply fixes.
2check-memory
Explicitly check memory system before answering or exploring
2