메뉴
Upgrades all project dependencies to latest compatible versions. Use when the user says "upgrade packages", "update deps", "bump dependencies", or "upgrade dependencies".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | upgrade-packages |
| description | Upgrades all project dependencies to latest compatible versions. Use when the user says "upgrade packages", "update deps", "bump dependencies", or "upgrade dependencies". |
| argument-hint | [--check-only] [--major] [specific-package-name] |
Upgrade all project dependencies to their latest compatible versions across all languages in the repo.
--check-only — List outdated packages without upgrading. Stop after Step 2.--major — Include major version bumps (breaking changes). Without this flag, stay within semver-compatible ranges.Scan the repo for these package ecosystems:
| Marker File | Ecosystem | Location |
|---|---|---|
Cargo.toml (workspace) | Rust (cargo) | Repo root |
package.json / package-lock.json | Node.js (npm) | editors/vscode/ |
*.csproj / *.fsproj / Directory.Build.props | C#/F# (.NET / NuGet) | sidecars/SharpLsp.Sidecars.sln |
Run the appropriate command to list what's outdated BEFORE upgrading anything. Show the user what will change.
cargo outdated --root-deps-only --workspace
cargo update --dry-run
If cargo-outdated is not installed: cargo install cargo-outdated
Read the docs: https://doc.rust-lang.org/cargo/commands/cargo-update.html
npm outdated --prefix editors/vscode
Read the docs: https://docs.npmjs.com/cli/v10/commands/npm-update
dotnet list sidecars/SharpLsp.Sidecars.sln package --outdated
For transitive dependencies too: dotnet list sidecars/SharpLsp.Sidecars.sln package --outdated --include-transitive
Read the docs: https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-list-package
If --check-only was passed, stop here and report the outdated list.
Before running any upgrade command, you MUST fetch and read the official documentation URL listed above for the detected package manager. Use WebFetch to retrieve the page. This ensures you use the correct flags and understand the behavior. Do not guess at flags or options from memory.
For any package with a major version bump (when --major is passed), also check the package's changelog or release notes for breaking changes before upgrading.
If a specific package name was given as an argument, upgrade only that package.
cargo update # semver-compatible updates
# --major flag:
cargo update --breaking # major version bumps (cargo 1.84+)
For workspace members, run from workspace root.
npm update --prefix editors/vscode # semver-compatible
# --major flag:
npx npm-check-updates -u --packageFile editors/vscode/package.json && npm install --prefix editors/vscode
dotnet outdated --upgrade sidecars/SharpLsp.Sidecars.sln
If dotnet-outdated tool is not installed: dotnet tool install -g dotnet-outdated-tool
Read the docs: https://github.com/dotnet-outdated/dotnet-outdated
Shared NuGet package versions live in Directory.Build.props — check there first and update centrally when possible, rather than editing individual .csproj/.fsproj files.
After upgrading, run the full CI pipeline:
make ci
If tests fail:
make ciProvide a summary:
--major flag)make ci after upgrading to catch breakage immediatelyCargo.lock, package-lock.json) — let the package manager regenerate themCargo.lock changes in the same commit as Cargo.toml changespackage-lock.json changes in the same commit as package.json changesDirectory.Build.props is the source of truth for shared .NET package versions — update there firstPrepares the current branch for CI by running the exact same steps locally and fixing issues. If CI is already failing, fetches the GH Actions logs first to diagnose. Use before pushing, when CI is red, or when the user says "fix ci".
Searches for duplicate code, duplicate tests, and dead code across the SharpLsp repo, then safely merges or removes them. Use when the user says "deduplicate", "find duplicates", "remove dead code", "DRY up", or "code dedup". Requires test coverage — refuses to touch untested code.
Audit spec/plan documents against the codebase. Ensures every spec section has implementing code, tests, and matching logic. Use when the user says "check specs", "spec audit", or "verify specs".
Audits a website for SEO, AI search performance, structured data, mobile usability, broken links, and social media cards. Fixes issues found. Use when the user mentions "audit website", "SEO", "fix search ranking", "AI search", "structured data", "social media cards", or "website performance".
Fix a bug using test-driven development. Use when the user reports a bug, describes unexpected behavior, wants to fix a defect, or says something is broken. Enforces a strict test-first workflow where a failing test must be written and verified before any fix is attempted.
Creates a pull request with a well-structured description after verifying CI passes. Use when the user asks to submit, create, or open a pull request.