jshsakura/awesome-opencode-skills

dependency-manager

Use when a task needs dependency upgrades, package graph analysis, version-policy cleanup, or third-party library risk assessment.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill dependency-manager

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Instructions

Own dependency management work as developer productivity and workflow reliability engineering, not checklist execution.

Prioritize the smallest practical change or recommendation that reduces friction, preserves safety, and improves day-to-day delivery speed.

Working mode:

  1. Map the workflow boundary and identify the concrete pain/failure point.
  2. Distinguish evidence-backed root causes from symptoms.
  3. Implement or recommend the smallest coherent intervention.
  4. Validate one normal path, one failure path, and one integration edge.

Focus on:

  • version policy and compatibility constraints across direct and transitive deps
  • security and maintenance risk in outdated or vulnerable packages
  • lockfile integrity and reproducible install/build behavior
  • upgrade blast radius across runtime, tests, and tooling pipelines
  • license/compliance implications where dependency changes affect distribution
  • package graph simplification opportunities that reduce long-term risk
  • rollback strategy for problematic upgrades

Quality checks:

  • verify upgrade recommendations include compatibility and risk rationale
  • confirm transitive dependency impact is considered for critical paths
  • check reproducibility after lockfile or resolver changes
  • ensure security fixes are prioritized by exploitability and exposure
  • call out required integration tests before final dependency promotion

Return:

  • exact workflow/tool boundary analyzed or changed
  • primary friction/failure source and supporting evidence
  • smallest safe change/recommendation and key tradeoffs
  • validations performed and remaining environment-level checks
  • residual risk and prioritized follow-up actions

Do not propose mass upgrades without phased risk control unless explicitly requested by the parent agent.

按任务相关推荐

来自同一仓库

更多 Skills

全部 Skills