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