dependency-conflict-resolver

Detect and resolve package dependency conflicts before installation.

91|10|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/marcusgoll/Spec-Flow --skill dependency-conflict-resolver-marcusgoll
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-conflict-resolver
Source: https://github.com/marcusgoll/Spec-Flow/tree/main/.codex/skills/dependency-conflict-resolver
Command: npx skills add https://github.com/marcusgoll/Spec-Flow --skill dependency-conflict-resolver-marcusgoll

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Early detection and resolution of dependency conflicts to prevent broken builds and security issues across ecosystems.

Core Features & Use Cases

  • Pre-install conflict analysis for npm/yarn/pnpm, pip/poetry, cargo, and composer
  • Auto-resolve safe conflicts (patches, dev deps)
  • Flag breaking changes and propose migration paths

Quick Start

Detect conflicts during package installation and apply safe fixes where possible.

Frequently Asked Questions about dependency-conflict-resolver

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

FAQPage Schema
How do I detect dependency conflicts before installing packages?

Dependency conflict detection analyzes package requirements across npm, yarn, pnpm, pip, poetry, cargo, and composer to identify peer and transitive conflicts before installation. The Skill auto-triggers on install commands, flags version constraint mismatches, and surfaces platform or runtime incompatibilities across JavaScript, Python, Rust, and PHP ecosystems to prevent broken builds.

Can dependency conflicts be automatically resolved during installation?

Safe conflicts—including patch updates and dev dependency mismatches—are auto-resolved without manual intervention. Breaking changes and risky fixes are flagged with risk classifications and migration path suggestions, requiring explicit review before application to prevent unintended behavior changes.

Does this work with multiple package managers at once?

Yes. The Skill supports npm, yarn, pnpm, pip, poetry, cargo, and composer, detecting and resolving conflicts uniformly across JavaScript, Python, Rust, and PHP projects. Multi-manager environments benefit from consistent conflict detection and structured resolution outputs.

How are security vulnerabilities handled during conflict resolution?

Security vulnerabilities are identified as part of pre-install analysis alongside peer and transitive conflicts. Vulnerable packages and their conflict sources are surfaced in structured resolution outputs with risk classifications, enabling informed decisions before installation.

What happens when a dependency conflict involves breaking changes?

Breaking changes trigger manual review prompts rather than auto-apply. The Skill provides migration path proposals and risk classifications so teams can evaluate trade-offs and decide whether to proceed, proceed with alternatives, or defer resolution.