Fähigkeiten dependency-upgrade
📦

dependency-upgrade

v1.0 Inhaltsrevision r1 Sicher ⚙️ Externe Befehle

Upgrade Dependencies With Focused Migration Checks

Dependency upgrades can introduce breaking changes and obscure existing failures. This skill guides focused migrations through release notes, baseline comparisons, minimal edits, and rollback reporting.

Unterstützt: Claude Codex Code(CC)
Maintain this Skill? Claim it 🥉 78 Bronze

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage
Review the Skillstore skill "dependency-upgrade" from https://skillstore.io/skills/agentkitco-dependency-upgrade.md and its manifest at https://skillstore.io/api/skills/agentkitco-dependency-upgrade/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Agent-lesbare Ressourcen

Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.

Testen

„dependency-upgrade“ wird verwendet. Show an example planning report for a major dependency upgrade.

Erwartetes Ergebnis:

  • Illustrative plan: confirm the installed version from the lockfile and select an explicit target.
  • Review intervening release notes and list affected API usages with file references.
  • Record baseline checks before changes and request approval for required runtime or peer upgrades.
  • Report verification differences and a rollback option after implementation.

„dependency-upgrade“ wird verwendet. Show an example response when an upgrade requires an unapproved runtime change.

Erwartetes Ergebnis:

  • Illustrative status: paused pending approval for the required runtime change.
  • Present the documented minimum runtime and explain why it expands the requested scope.
  • Ask whether to approve the runtime change or consider another target version.
  • Identify checks not completed and avoid claiming the migration passed.

Sicherheitsaudit

Sicher
v2 • 22.10.2026 Versionsbericht öffnen

All five static findings are false positives involving Markdown backticks, routine package version queries, code search, and rollback documentation. No evidence found of malicious intent, credential access, data exfiltration, or prompt injection in SKILL.md.

1
Gescannte Dateien
48
Analysierte Zeilen
0
Prüfelemente
0
Falschmeldungen ignoriert
Das letzte abgeschlossene statische und semantische Audit erkannte keine bestätigten Sicherheitsbefunde. Dies beweist nicht, dass der Skill keine Nebenwirkungen hat.
Geprüft von: codex Audit-Verlauf anzeigen →
Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen
Sicherheitsbewertung

Berichtslink kopieren

https://skillstore.io/skills/agentkitco-dependency-upgrade/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown-Badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/agentkitco-dependency-upgrade/security.svg)](https://skillstore.io/skills/agentkitco-dependency-upgrade?utm_source=security_passport_badge)

HTML-Badge

<a href="https://skillstore.io/skills/agentkitco-dependency-upgrade?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/agentkitco-dependency-upgrade/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Einbettungskarte

<iframe src="https://skillstore.io/embed/skills/agentkitco-dependency-upgrade.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

agentkitco. (2026). dependency-upgrade security audit report (audit version 2) [Author version 1.0]. Skillstore. https://skillstore.io/skills/agentkitco-dependency-upgrade/audits/2

BibTeX-Zitat

@techreport{agentkitco-agentkitco-dependency-upgrade-2026, author = {agentkitco}, title = {dependency-upgrade security audit report (audit version 2)}, institution = {Skillstore}, year = {2026}, number = {2}, url = {https://skillstore.io/skills/agentkitco-dependency-upgrade/audits/2}, note = {Author version 1.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "dependency-upgrade security audit report (audit version 2)" version: "1.0" type: report authors: - name: "agentkitco" date-released: "2026-10-22" url: "https://skillstore.io/skills/agentkitco-dependency-upgrade/audits/2" identifiers: - type: other value: "skillstore:agentkitco-dependency-upgrade:audit:2" description: "Skillstore immutable audit report identifier"

Varianten vergleichen

3 installierbare Varianten

Jeder Autor bleibt ein eigener installierbarer Skill. Die empfohlene Variante wird nach Skillstore-Nachweisen bewertet.

Warum diese Variante zuerst steht

Höhere Evidenzsicherheit
sickn33 Empfohlen

sickn33-dependency-upgrade

Skillstore-Score 78
Evidenzvertrauen Hoch
Skillstore-Nutzung 16
Aktualisiert

2026-09-09

agentkitco Aktuell

agentkitco-dependency-upgrade

Skillstore-Score 78
Evidenzvertrauen Mittel
Skillstore-Nutzung 7
Aktualisiert

2026-10-22

wshobson-dependency-upgrade

Skillstore-Score 69
Evidenzvertrauen Hoch
Skillstore-Nutzung 16
Aktualisiert

2026-09-09

Skillstore-Score

Warum dieser Score Evidenzvertrauen: Mittel
55
Architektur
85
Wartbarkeit
87
Inhalt
65
Gemeinschaft
91
Spezifikationskonformität

Was Sie erstellen können

Update an application library

Inspect release notes, identify affected APIs, update one package, and compare project checks against the baseline.

Prepare a framework migration

Map major-version changes, identify runtime and peer requirements, and request approval before expanding the upgrade scope.

Document a security-related upgrade

Upgrade an affected dependency and cite an advisory only when official documentation supports the security claim.

Diese Prompts ausprobieren

Inspect an upgrade target
Check the installed version of [package] and identify the latest release. Summarize relevant release notes without changing files.
Perform a focused upgrade
Upgrade [package] to [target version]. Record baseline checks, review release notes, update affected code, and compare verification results.
Plan a major migration
Plan the migration of [framework] from [current version] to [target version]. Map breaking APIs and request approval for runtime or peer changes.
Resolve conflicts with evidence
Investigate [package] upgrade conflicts without overriding dependency constraints. Present conflict output, options, official advisory evidence if applicable, verification gaps, and rollback guidance.

Bewährte Praktiken

  • Start with a clean working tree and record existing failures before changing dependencies.
  • Use the project package manager for manifest and lockfile updates, and cite release notes for applicable changes.
  • Compare verification results with the baseline and document skipped checks, remaining warnings, and rollback steps.

Vermeiden

  • Running a blanket dependency update when the request concerns one package.
  • Combining an upgrade with unrelated refactoring or changing runtime requirements without approval.
  • Skipping failing tests, loosening version ranges, or overriding conflicts to conceal compatibility problems.

Häufig gestellte Fragen

Which assistants can use this skill?
The listing supports Claude, Codex, and Claude Code. Practical execution requires repository access and the tools needed for the project.
Does this skill include an automated upgrade script?
No. It contains a Markdown workflow that guides an assistant through planning, edits, verification, and reporting.
Can it upgrade multiple dependencies together?
It focuses on one dependency or a tightly coupled group, including required peers. It explicitly rejects blanket updates.
What happens when release notes are missing?
The workflow requires stating that release notes are unavailable and treating the upgrade as higher risk.
Will it change runtime requirements automatically?
No. It requires stopping and asking before changing minimum runtime or peer versions.
Can it prove that an upgrade fixes a vulnerability?
It permits security claims only when supported by an official advisory or release notes. It does not provide an independent vulnerability scanner.

Entwicklerdetails

Lizenz

MIT

Autorenversion

v1.0

Skillstore-Revision

r1

Versionshinweis

Die vom Autor angegebene Version ist kein gültiges SemVer.

Ref.

18efac79a818d7e997295839638fdd21906cfd1c

Aktualität der Wartung

22.10.2026

Nutzung

5 Downloads · 0 Aufrufe

Dateistruktur

📄 SKILL.md