gemfile-upgrade
Safely upgrade a Ruby gem with changelog review, breaking changes analysis, bundle update, test run, and commit. Use when the user asks to upgrade, bump, or update a gem, or to review outdated gems.
What this skill does
# Gemfile Upgrade
## Input
- ARG = `gem_name` (single gem) | `--outdated` (batch mode)
## Workflow (single gem)
1. Check status:
```bash
bundle outdated GEM --strict
```
Parse: current, latest, jump type (patch/minor/major)
2. Locate repo:
```bash
bundle info GEM --path # check gemspec for homepage / source_code_uri
```
3. Fetch changelog via WebFetch (try in order, stop on first hit):
- `https://github.com/OWNER/REPO/releases`
- `https://github.com/OWNER/REPO/blob/main/CHANGELOG.md`
- `https://github.com/OWNER/REPO/blob/main/HISTORY.md`
- `https://github.com/OWNER/REPO/blob/main/NEWS.md`
4. Extract changes between current → target. Flag:
- Major bumps (X.x → Y.x)
- Keywords: `BREAKING`, `removed`, `renamed`, `changed behavior`
- Migration guides
- Ruby/Rails version requirements
- Deprecations
5. Present analysis:
```
## Upgrade Analysis: GEM CURRENT → TARGET
### Version Jump: PATCH | MINOR | MAJOR
### Breaking Changes: [list]
### Migration Required: [steps]
### Deprecations: [list]
### New Features: [list]
### Compatibility: [Ruby/Rails reqs]
```
6. AskUserQuestion → options:
- `Upgrade to latest minor (recommended)` — safer, bug fixes
- `Upgrade to latest (TARGET)` — review breaking changes
- `Upgrade to specific version` — prompt for version
- `Skip`
7. Update Gemfile (Edit):
```ruby
# latest
gem 'GEM', '~> MAJOR.MINOR'
# minor only
gem 'GEM', '~> CURRENT_MAJOR.CURRENT_MINOR'
```
8. Run update:
```bash
bundle update GEM --conservative
```
On failure → show conflicts, suggest dependent updates, offer rollback.
9. Run tests (auto-detect):
```bash
if [ -f spec/spec_helper.rb ]; then bundle exec rspec
elif [ -f test/test_helper.rb ]; then bundle exec rails test
fi
```
- Pass → step 10
- Fail → show failures, AskUserQuestion: `Rollback` | `Investigate`
10. Commit:
```bash
git add Gemfile Gemfile.lock
git commit -m "$(cat <<'EOF'
chore(deps): upgrade GEM from CURRENT to TARGET
Breaking changes:
- [list]
Migration notes:
- [steps taken]
Changelog: URL
EOF
)"
```
## Workflow (--outdated batch mode)
1. `bundle outdated --strict`
2. Group by jump type:
- **PATCH** (X.Y.Z → X.Y.Z+1) — usually safe
- **MINOR** (X.Y → X.Y+1) — review recommended
- **MAJOR** (X → X+1) — careful review required
3. AskUserQuestion (multi-select) presenting all gems grouped by risk
4. For each selected gem → run single-gem workflow (steps 1-10)
## Rollback
At any failure step:
```bash
git checkout -- Gemfile Gemfile.lock
bundle install
```
## Safety Rules
- Always show diff before applying
- Create backup of Gemfile before edit (Edit tool preserves prior content via git)
- Never commit if tests fail
- Default to `--conservative` to avoid cascading updates
- Flag major version jumps explicitly in analysis
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.