upgrade-dependency
Skill88 starsChanged 20 days agoMITView on GitHub
升级项目中的指定依赖包到新版本并验证变更。 当需要升级某个依赖并验证改动时使用。参数:包名、原版本和新版本。
- Installs packages
4 other projects use a version of this.
Adopted by
Most recently taken up by
- malinskibeniamin/skillstheir own version, first seen Oct 17, 2026
- ModelEngine-Group/fit-frameworktheir own version, first seen Oct 8, 2026
- awcameron/skillstheir own version, first seen Sep 30, 2026
- warsab/ai-skillstheir own version, first seen Aug 26, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- ModelEngine-Group/fit-framework★ 2.1ksame name
- malinskibeniamin/skills★ 4same name
- awcameron/skills★ 2same name
- warsab/ai-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyze-taskSkill
- archive-tasksSkill
- block-taskSkill
- cancel-taskSkill
- check-taskSkill
- close-codescanSkill
- close-dependabotSkill
- code-taskSkill
- commitSkill
- complete-manual-validationSkill
- complete-taskSkill
- create-prSkill
- create-release-noteSkill
- create-taskSkill
- entropy-checkSkill
- import-codescanSkill
- import-dependabotSkill
- import-issueSkill
- init-labelsSkill
- init-milestonesSkill
- plan-taskSkill
- post-releaseSkill
- refine-titleSkill
- releaseSkill
- restore-taskSkill
- review-analysisSkill
- review-codeSkill
- review-planSkill
- review-prSkill
- run-manual-validationSkill
- test-integrationSkill
- testSkill
- update-agent-infraSkill
- watch-prSkill
The file
Files
升级依赖
将依赖包升级到指定版本,并进行构建和测试验证。
本项目使用 npm、package.json 和 package-lock.json 管理依赖。
执行流程
1. 解析参数
从参数中提取:包名、原版本、新版本。
2. 查找依赖位置
在 package.json 和 package-lock.json 中确认目标包、当前版本和依赖类型。
3. 更新版本
使用 npm 更新依赖并同步 lockfile:
npm install {package}@{new-version}4. 验证类型与核心测试
npm run typecheck
npm run test:corenpm run test:core 会先构建项目。
5. 运行完整测试(高风险升级)
主版本升级、构建工具升级或影响多个运行路径时执行:
npm test6. 输出结果
报告:
- 修改的文件
- 构建状态(通过/失败)
- 测试状态(通过/失败)
- 发现的任何弃用警告或破坏性变更
建议下一步:
渲染下一步前先读取
.agents/rules/next-step-output.md,仅为已选场景调用统一 helper,并将 stdout 填入{next-step-commands}。
使用 agent-infra-internal agent-client next-steps --skill commit 生成本场景的 {next-step-commands}。
下一步 - 提交代码:
{next-step-commands}注意事项
- 禁止自动提交:不要自动提交变更
- 主版本升级:警告潜在的破坏性变更
- 测试失败:先检查证据并修复任务范围内可诊断的问题,再运行相同验证;涉及范围外设计、用户数据冲突或必要授权时记录阻塞并继续独立工作
- 锁文件:如果项目使用锁文件(package-lock.json、yarn.lock 等),确保一并更新
- 传递依赖:注意升级是否影响传递依赖
错误处理
- 包未找到:提示 "Package {name} not found in dependency files"
- 构建失败:输出错误并建议检查破坏性变更
- 测试失败:先诊断并修复任务范围内可恢复的问题,再按同一验证器复测;必要时记录迁移指南相关风险
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

