release
Release Workflow
Automate the full release lifecycle for the ClaudeMemory gem. This workflow was codified from the actual 0.9.0 release process.
The release has three phases: prepare (automated), publish (user-driven), and announce (automated). The middle phase requires user action because it pushes to a shared remote and publishes to RubyGems — destructive operations that must never happen without explicit confirmation.
Phase 1: Prepare
Step 1: Determine the new version
If a version was passed as an argument, use it. Otherwise, read the current version from lib/claude_memory/version.rb and ask the user what the new version should be.
Step 2: Find and update all version references
The version lives in exactly three files. Grep to confirm there are no others:
grep -rn "CURRENT_VERSION" --include="*.rb" --include="*.json" --include="*.gemspec" . | grep -v "CHANGELOG\|node_modules\|vendor\|\.git/"
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.
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.
2check-memory
Explicitly check memory system before answering or exploring
2