mohitagw15856/dependency-conflict-resolver
plugins/pm-engineering/skills/dependency-conflict-resolver/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add mohitagw15856/pm-claude-skills dependency-conflict-resolverInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 21, 2026, 5:55 AM94.5s1 file scanned
SKILL.md
- name:
- dependency-conflict-resolver
- description:
- 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.
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
The install error / conflict output, plus (if given) the manifest (package.json, requirements.txt, go.mod…) and lockfile, and the manager. 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)
- Safest — e.g. align versions, upgrade the constrained package, or find a compatible range. Exact command.
- Pragmatic — e.g. an override/resolution (
overrides,resolutions, constraints file) with the exact snippet — and the risk it carries. - 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
Related Skills
mohitagw15856/win-loss-analysis
business
VerifiedTrustedCommunity
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/which-skill
development
VerifiedTrustedCommunity
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/vuln-triage
testing
VerifiedTrustedCommunity
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
1,117SKILL.mdUpdated Jul 2, 2026
mohitagw15856/voice-of-customer-program
development
VerifiedTrustedCommunity
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.
1,117SKILL.mdUpdated Jul 2, 2026