claude_memory

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.

Deep analysis of an external repository's architecture, patterns, and design decisions. Generates comprehensive influence document and updates improvements.md with prioritized recommendations.

Launch a local web dashboard for ClaudeMemory debugging and observability

Upgrade all Ruby gem dependencies to their latest versions with release note review and codebase alignment checks. Use this skill whenever the user asks to update, upgrade, or bump dependencies, gems, or packages — even casually like 'update my gems' or 'are my deps up to date?'

Incrementally implement feature improvements from docs/improvements.md with tests and atomic commits. Focuses on new functionality rather than refactoring.

Automatically install, configure, or upgrade ClaudeMemory

Explicitly check memory system before answering or exploring

Diagnose ClaudeMemory installation and configuration issues. Use when memory tools fail or setup seems broken.

Workflow for checking memory before code exploration. Auto-loaded when answering questions about code, architecture, or patterns.

Quick quality review of staged changes for pre-commit validation. Checks Ruby best practices and flags critical issues.

Incrementally implement code quality improvements from docs/quality_review.md with tests and atomic commits. Run after /review-for-quality to apply fixes.

Comprehensive code quality review through expert perspectives (Sandi Metz, Jeremy Evans, Kent Beck, Avdi Grimm, Gary Bernhardt). Updates docs/quality_review.md with findings.

Knowledge about analyzing projects for tech stack, frameworks, tools, and conventions. Use when asked to understand or learn about a project's structure.

Store and recall long-term memory. Use when persisting facts learned during conversations or recalling stored knowledge about projects and preferences.