SkillsAdd

mohitagw15856/pm-claude-skills

dependency-conflict-resolver

Resolve a dependency or version conflict (npm, pip, yarn, pnpm, Maven, Go modules) step by step.

First seen Jun 21, 2026

Installation

$ npx skills add mohitagw15856/pm-claude-skills --skill dependency-conflict-resolver
View on skills.sh ↗ GitHub repository ↗

Summary

  • Resolve a dependency or version conflict (npm, pip, yarn, pnpm, Maven, Go modules) step by step.
  • Use when an install fails with peer-dependency or version-conflict errors, packages won't co-exist, or a lockfile is fighting you.
  • Produces the conflict explained, the resolution options ranked by safety, exact commands, and how to keep it from recurring.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

golang-dependency-management Similar name
samber/cc-skills-golang

Dependency management for Golang projects — go.mod and go.sum, `go get` install and upgrade flo…

37.1K installs
golang-dependency-injection Similar name
samber/cc-skills-golang

Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability…

36.9K installs
dependency-upgrade Similar name
wshobson/agents

Manage major dependency version upgrades with compatibility analysis, staged rollout, and compr…

9.8K installs
dependency-updater Similar name
softaworks/agent-toolkit

Smart dependency management for any language. Auto-detects project type, applies safe updates a…

3.9K installs
dependency-confusion Similar name
yaklang/hack-skills

>- Supply-chain testing via package-manager dependency confusion: when internal package names r…

2.9K installs
spring-boot-dependency-injection Similar name
giuseppe-trisciuoglio/developer-kit

Provides dependency injection patterns for Spring Boot projects, including constructor-first de…

2.8K installs

Also in this package

Other skills from mohitagw15856/pm-claude-skills · top by installs.

npx skills add mohitagw15856/pm-claude-skills
teaching-lesson-plan 150 team-offsite-planner 98 sop-writer 72 patient-communication 67 user-research-synthesis 66 financial-due-diligence 65 competitive-analysis 65 prd-template 64 meeting-notes 62 project-status-report 62

Browse all from mohitagw15856/pm-claude-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1.3K
License LICENSE
Default branch main
Open issues 7
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,669 B
  • docs SUMMARY.md 388 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 14 installs

SKILL.md

Dependency Conflict Resolver Skill

Untangle "could not resolve dependency" hell into a clear, ranked plan.

Working from a brief

Infer the package manager and ecosystem from the error or files mentioned; label assumptions (assumed — confirm). Always deliver a concrete resolution path even from just the error text.

Input

Ask for these if not provided:

  • The install error — the conflict output exactly as the tool printed it
  • The manifest — package.json, requirements.txt, go.mod, pom.xml, whichever applies
  • The lockfile — if one exists, since it is usually where the conflict is pinned
  • The package manager — npm, pnpm, yarn, pip, Maven, Go modules; infer what's missing

Output Structure

The conflict

Plain-English: package A needs X of C, package B needs Y of C, and they can't both be satisfied (name the actual packages/versions from the input).

Options (ranked by safety)

  1. Safest — e.g. align versions, upgrade the constrained package, or find a compatible range. Exact command.
  2. Pragmatic — e.g. an override/resolution (overrides, resolutions, constraints file) with the exact snippet — and the risk it carries.
  3. Last resort — e.g. --legacy-peer-deps / --force — clearly flagged as masking the problem, not fixing it.

Give the exact commands/edits for each, and a recommendation of which to pick and why.

Verify & prevent

How to confirm the fix (npm ls <pkg>, a clean reinstall, the build), and one habit to avoid recurrence (lockfile committed, renovate/dependabot, version pinning policy).

Quality Checks

  • Names the actual conflicting packages and versions from the input
  • Options are ranked by safety with the trade-off of each stated
  • --force/--legacy-peer-deps-style escapes are flagged as masking, not fixing
  • Includes a verification step

Anti-Patterns

  • Do not lead with --force / --legacy-peer-deps — it hides the conflict and breaks later
  • Do not delete the lockfile as the first move — explain what that actually does
  • Do not give a single fix when several are viable — rank them with trade-offs
  • Do not skip verifying the resolution actually installs/builds