Mode d’emploi
- Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
- Consultez le document original pour les outils, identifiants et environnements requis.
- Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill gemfile-upgradeAvant de commencer
- L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
- Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original
Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.
Gemfile Upgrade
Input
- ARG =
gem_name(single gem) |--outdated(batch mode)
Workflow (single gem)
- Check status:
bash
bundle outdated GEM --strictParse: current, latest, jump type (patch/minor/major)
- Locate repo:
bash
bundle info GEM --path # check gemspec for homepage / source_code_uri- Fetch changelog via WebFetch (try in order, stop on first hit):
https://github.com/OWNER/REPO/releaseshttps://github.com/OWNER/REPO/blob/main/CHANGELOG.mdhttps://github.com/OWNER/REPO/blob/main/HISTORY.mdhttps://github.com/OWNER/REPO/blob/main/NEWS.md
- 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
- 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]- AskUserQuestion → options:
Upgrade to latest minor (recommended)— safer, bug fixesUpgrade to latest (TARGET)— review breaking changesUpgrade to specific version— prompt for versionSkip
- Update Gemfile (Edit):
ruby
# latest
gem 'GEM', '~> MAJOR.MINOR'
# minor only
gem 'GEM', '~> CURRENT_MAJOR.CURRENT_MINOR'- Run update:
bash
bundle update GEM --conservativeOn failure → show conflicts, suggest dependent updates, offer rollback.
- 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
- 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)
bundle outdated --strict- 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
- AskUserQuestion (multi-select) presenting all gems grouped by risk
- For each selected gem → run single-gem workflow (steps 1-10)
Rollback
At any failure step:
bash
git checkout -- Gemfile Gemfile.lock
bundle installSafety 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
--conservativeto avoid cascading updates - Flag major version jumps explicitly in analysis
