Token导航 LogoToken导航

Agent Skill · 开发

cuihua-dependency-updater(翠花依赖更新器)

cuihua-dependency-updater 用于辅助前端页面、组件、样式和交互逻辑开发,适合在 OpenClaw 中需要维护前端项目、生成组件或检查界面实现时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

cuihua-dependency-updater 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描有提醒项,按安装量在开发类的 21,746 个 Skill 里排第 8,077。

总安装 3,352周安装 144GitHub Stars 公开资料未说明下载 1,175核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:cuihua-dependency-updater(翠花依赖更新器)
来源仓库:https://github.com/supermario11/cuihua-dependency-updater
安装命令:
openclaw skills install cuihua-dependency-updater
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install cuihua-dependency-updater

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

用于辅助前端页面、组件、样式和交互逻辑开发,适合在 OpenClaw 中需要维护前端项目时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

AI 支持的依赖更新助手,通过安全检查、重大变更检测和自动化测试来智能更新 npm/yarn 包。保持项目依赖最新并确保兼容性和安全性。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install cuihua-dependency-updater;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

cuihua-dependency-updater 怎么安装?

在终端执行 openclaw skills install cuihua-dependency-updater。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

cuihua-dependency-updater 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

cuihua-dependency-updater 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

cuihua-dependency-updater 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

cuihua-dependency-updater 用的人多吗?

公开数据是累计安装 3,352 次,近一周安装 144 次,下载 1,175 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

cuihua-dependency-updater 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
cuihua-dependency-updater

翠花依赖更新器 · 本页

3,352—需要联网MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
cuihua-dependency-updater
description
|
metadata
openclaw
requires
bins
[node, npm]
env
[]
primaryEnv
null
version
1.0.0
author
翠花 (Cuihua) - ClawHub Pioneer
license
MIT
tags
capabilities

cuihua-dependency-updater 📦

Keep dependencies fresh, keep your app safe

AI-powered dependency management that updates packages intelligently:

  • 🔒 Security-first - Prioritize security patches
  • 🛡️ Safe updates - Detect breaking changes before updating
  • 🤖 Smart batching - Group compatible updates
  • 📝 Auto changelog - Generate update summaries
  • ⏮️ Easy rollback - Undo problematic updates

🎯 Why cuihua-dependency-updater?

The problem:

  • ❌ npm outdated shows 50+ packages to update
  • ❌ No idea which ones are safe to update
  • ❌ Breaking changes break your app
  • ❌ Security patches mixed with feature updates
  • ❌ Manual updates take hours

cuihua-dependency-updater solves this.


🚀 Quick Start

Check for updates

"Check outdated dependencies"

Output:

📦 Dependency Update Report
━━━━━━━━━━━━━━━━━━━━━━━━

🔴 Security updates (3):
  - lodash: 4.17.19 → 4.17.21 (CVE-2020-8203)
  - minimist: 1.2.5 → 1.2.6 (CVE-2021-44906)
  - axios: 0.21.1 → 1.6.0 (CVE-2023-45857)

🟡 Breaking changes (2):
  - webpack: 4.46.0 → 5.89.0 (Major version)
  - react: 17.0.2 → 18.2.0 (Major version)

🟢 Safe updates (12):
  - typescript: 4.9.5 → 5.3.3 (Minor)
  - eslint: 8.50.0 → 8.56.0 (Patch)
  ...

💡 Recommendation: Update security first

Update by priority

"Update security vulnerabilities"

Generated:

npm update lodash minimist axios
npm audit fix

Smart batch update

"Update all safe dependencies"

Automatically:

  1. Groups compatible updates
  2. Tests each batch
  3. Rolls back if tests fail
  4. Generates changelog

🎨 Features

1. Intelligent Prioritization 🎯

Updates are categorized by risk and impact:

{
  "security": [
    { package: "lodash", severity: "high", cve: "CVE-2020-8203" }
  ],
  "breaking": [
    { package: "webpack", from: "4.x", to: "5.x", impact: "high" }
  ],
  "safe": [
    { package: "typescript", from: "4.9", to: "5.3", impact: "low" }
  ]
}

2. Breaking Change Detection 🔍

AI analyzes changelogs and API changes:

⚠️  Breaking changes detected in react@18:

1. ReactDOM.render → createRoot
   Impact: ALL entry points need updates
   
2. Automatic batching
   Impact: State updates may batch differently
   
3. Stricter hydration
   Impact: SSR apps may break

Recommendation: Schedule major update separately
Estimated effort: 2-4 hours

3. Security Scanning 🔒

Integrates with npm audit and vulnerability databases:

🔴 HIGH severity vulnerability
━━━━━━━━━━━━━━━━━━━━━━━━━━━

Package: lodash@4.17.19
CVE: CVE-2020-8203
Severity: HIGH
Impact: Prototype pollution

Affected paths:
  - app → lodash (direct)
  - webpack → lodash (indirect)

Fix available: lodash@4.17.21
Risk: LOW (patch version)

🚀 Safe to update immediately

4. Automated Testing 🧪

Run tests after each update batch:

async function safeUpdate(packages) {
  // Backup current state
  const backup = await saveState();
  
  try {
    // Update packages
    await npm.update(packages);
    
    // Run tests
    const testsPassed = await runTests();
    
    if (!testsPassed) {
      throw new Error('Tests failed');
    }
    
    console.log('✅ Update successful');
    
  } catch (error) {
    // Rollback on failure
    await restore(backup);
    console.log('⏮️  Rolled back due to:', error.message);
  }
}

5. Changelog Generation 📝

Auto-generate human-readable update summaries:

# Dependency Updates - 2026-03-24

## Security Fixes (3)
- lodash: 4.17.19 → 4.17.21
  - Fixed: Prototype pollution vulnerability
  - CVE: CVE-2020-8203
  
- axios: 0.21.1 → 1.6.0
  - Fixed: SSRF vulnerability
  - CVE: CVE-2023-45857

## Feature Updates (5)
- typescript: 4.9.5 → 5.3.3
  - Added: Better type inference
  - Added: Decorators support
  
- eslint: 8.50.0 → 8.56.0
  - Fixed: Several bugs
  - Added: New rules

## Breaking Changes (Postponed)
- webpack: 4.46.0 → 5.89.0
  - Reason: Requires configuration migration
  - Estimated effort: 4 hours
  - Scheduled: Next sprint

📋 Usage Examples

Example 1: Security Audit

User: "Audit dependencies for security issues"

Agent:

🔍 Security Audit Report
━━━━━━━━━━━━━━━━━━━━━━

Total packages: 1,234
Vulnerabilities: 8

🔴 CRITICAL (1)
  - express-fileupload@1.1.7
    CVE-2020-7699 (RCE)
    Fix: Update to 1.4.0

🟠 HIGH (3)
  - lodash@4.17.19 → 4.17.21
  - minimist@1.2.5 → 1.2.6
  - axios@0.21.1 → 1.6.0

🟡 MEDIUM (4)
  - qs@6.5.2 → 6.11.0
  - ...

💡 Action: npm audit fix --force
Risk: All fixes are patch/minor versions

Example 2: Major Version Update

User: "Can I safely update React to v18?"

Agent:

🔍 Analyzing React 17 → 18 migration...

✅ Compatibility Check:
  - react-dom: Compatible
  - react-router: Needs update to v6
  - redux: Compatible
  - typescript: Compatible

⚠️  Breaking Changes:
  1. ReactDOM.render API removed
     Files affected: 2 (src/index.js, src/test-utils.js)
     
  2. Automatic batching changes
     Potential impact: State update timing
     
  3. Stricter TypeScript types
     Files affected: 15

📊 Migration complexity: MEDIUM
Estimated time: 2-3 hours
Recommendation: Update in separate PR

🔧 Migration steps:
  1. Update packages
  2. Replace ReactDOM.render
  3. Fix TypeScript errors
  4. Test thoroughly
  
Want me to generate a migration guide?

Example 3: Batch Update

User: "Update all safe dependencies"

Agent:

📦 Preparing batch update...

Grouped into 3 batches:

Batch 1 (Testing tools - 5 packages):
  - jest: 29.5.0 → 29.7.0
  - @testing-library/react: 14.0.0 → 14.1.2
  - ...

Batch 2 (Build tools - 4 packages):
  - vite: 5.0.0 → 5.0.10
  - esbuild: 0.19.0 → 0.19.11
  - ...

Batch 3 (Utils - 8 packages):
  - date-fns: 2.30.0 → 3.0.6
  - lodash: 4.17.19 → 4.17.21
  - ...

Process:
1. Update Batch 1 → Run tests → ✅
2. Update Batch 2 → Run tests → ✅
3. Update Batch 3 → Run tests → ✅

✅ All updates successful!
📝 Changelog: UPDATES.md

⚙️ Configuration

Create .dependencyrc.json:

{
  "updateStrategy": "conservative",
  "priorities": [
    "security",
    "patch",
    "minor",
    "major"
  ],
  "autoUpdate": {
    "security": true,
    "patch": true,
    "minor": false,
    "major": false
  },
  "testing": {
    "runTests": true,
    "testCommand": "npm test",
    "rollbackOnFail": true
  },
  "exclude": [
    "react",
    "webpack"
  ],
  "changelog": {
    "generate": true,
    "path": "./UPDATES.md"
  }
}

🔧 Update Strategies

Conservative (Default)

  • Security: Auto-update
  • Patch: Auto-update
  • Minor: Manual review
  • Major: Manual review

Aggressive

  • Security: Auto-update
  • Patch: Auto-update
  • Minor: Auto-update
  • Major: Manual review

Custom

Define your own rules per package:

{
  "packages": {
    "lodash": "aggressive",
    "react": "manual",
    "typescript": "conservative"
  }
}

💰 Pricing

Free

  • ✅ Dependency analysis
  • ✅ Security scanning
  • ✅ Up to 100 packages

Pro ($10/month)

  • ✅ Unlimited packages
  • ✅ Automated updates
  • ✅ CI/CD integration
  • ✅ Custom strategies

Enterprise ($79/month)

  • ✅ Team policies
  • ✅ Monorepo support
  • ✅ Advanced rollback
  • ✅ Compliance reports

📚 Resources


📜 License

MIT


🙏 Acknowledgments

Built with 🌸 by 翠花 (Cuihua)


Made with 🌸 | Cuihua Series | ClawHub Pioneer

_Keep dependencies fresh, keep your app safe._

平台分布

OpenClaw

73%
按下载量换算858

安全审计

VirusTotal

未展示

Static analysis

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills