upgrade-dependencies
Dependency Upgrade Skill
Systematically upgrade Ruby gem dependencies by researching latest versions, reviewing release notes for breaking changes, updating version constraints, verifying with tests, and confirming codebase alignment.
The goal is a thoughtful upgrade — not blindly bumping versions, but understanding what changed and ensuring the codebase is compatible. This matters because a silent API change can introduce bugs that tests don't catch if the tests don't exercise the affected code path.
Process Overview
- Discover current dependencies and their constraints
- Research latest versions and release notes (in parallel)
- Analyze breaking changes and codebase impact
- Upgrade version constraints and install
- Verify with the full test suite
- Report a summary table with upgrade details
Step 1: Discover Current Dependencies
Read the gemspec and Gemfile to build a complete dependency inventory.
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