kb-dependency-management

Detect and coordinate dependency updates across package managers with build verification.

2|Updated Mar 11, 2026

Search Tags:#automation #git-workflow #dependency-management #package-managers #build-verification #version-update #ecosystem-detection

Ready to run

npx skills add https://github.com/Conava/claude-devline --skill kb-dependency-management

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kb-dependency-management
Source: https://github.com/Conava/claude-devline/tree/main/skills/kb-dependency-management
Command: npx skills add https://github.com/Conava/claude-devline --skill kb-dependency-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Domain logic for dependency management — injected into the dependency-patcher agent. Provides ecosystem detection, version update mechanics, build/test verification, and commit/push workflows across all major package managers. Not invoked directly.

Core Features & Use Cases

Detect ecosystems across multiple manifests (e.g., package.json, pom.xml, pyproject.toml) and identify available lockfiles.
Update dependencies consistently across ecosystems, handling properties and catalog entries where relevant.
Verify builds and tests after updates, and prepare commits for review and deployment.

Quick Start

Invoke the dependency management workflow on a repository to detect ecosystems, plan updates, verify builds, and push changes.

Frequently Asked Questions about kb-dependency-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I update dependencies across multiple package managers like npm, pip, and maven in one workflow?▼

Multi-ecosystem dependency updates are coordinated by detecting manifests like package.json and pom.xml, applying version updates across package managers, verifying builds, and preparing automated git commits.

What is the best way to detect all package ecosystems and lockfiles in a repository before updating versions?▼

Ecosystem detection works by scanning repository manifests such as pyproject.toml and pom.xml to identify available lockfiles and coordinate consistent dependency updates across all detected package managers.

Can I automate git commits and pushes after verifying dependency updates and build tests?▼

Yes, automated git commits and pushes are supported after dependency updates are applied and builds with tests are verified, aligning with the launcher's safety rules to prepare changelogs and commit messages.

Does dependency management support property-based version resolution and catalog entries?▼

Dependency management supports property-based version resolution and handles catalog entries where relevant, ensuring updates are applied consistently across ecosystems like maven and gradle.

How do I update lockfiles consistently when upgrading dependencies across different ecosystems?▼

Lockfile updates are handled automatically during the dependency update workflow, ensuring that detected lockfiles across ecosystems like npm, yarn, pip, and gradle remain synchronized with manifest changes.

Why do I need build verification after applying dependency updates across multiple package managers?▼

Build verification after dependency updates ensures compatibility across all ecosystems, confirming that version changes in manifests and lockfiles do not break existing builds or tests before committing.