quality-update
Quality Update - Incremental Implementation
Systematically implement code quality improvements from the review document, making tested, atomic commits for each fix.
Process Overview
- Read the quality review from
docs/quality_review.md - Prioritize improvements (start with Quick Wins, then High Priority)
- Implement fixes incrementally (one logical change at a time)
- Run tests after each change to ensure nothing breaks
- Make atomic commits that capture the change and its purpose
- Update review document to track progress
Detailed Steps
Step 1: Read and Parse Review
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
2check-memory
Explicitly check memory system before answering or exploring
2