check-memory
Check Memory First
When invoked with /check-memory <topic>, this skill forces a memory-first workflow.
Task
IMPORTANT: You MUST check memory BEFORE reading any files or running any code searches.
The user is asking about: $ARGUMENTS
Step-by-Step Workflow
0. Verify Memory Health
Before querying, confirm the memory system is operational:
memory.check_setup
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.
2memory
Store and recall long-term memory. Use when persisting facts learned during conversations or recalling stored knowledge about projects and preferences.
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.
2