Summary
When two skills install to the same name/path, or when transitive dependencies create version conflicts, agr should detect this and report it clearly rather than silently overwriting.
Why
This is the safety net that makes the dependency graph trustworthy. Without conflict detection, users can unknowingly overwrite skills or end up with incompatible versions. This is a prerequisite for safe transitive dependency resolution.
Scope
- Detect name collisions when multiple skills resolve to the same install path
- Detect version conflicts when the same skill is required at different versions
- Report conflicts clearly with actionable error messages
- Support
--overwrite or similar flag to explicitly resolve conflicts
- Integrate with the dependency graph for transitive conflict detection
🤖 Generated with Claude Code
Summary
When two skills install to the same name/path, or when transitive dependencies create version conflicts, agr should detect this and report it clearly rather than silently overwriting.
Why
This is the safety net that makes the dependency graph trustworthy. Without conflict detection, users can unknowingly overwrite skills or end up with incompatible versions. This is a prerequisite for safe transitive dependency resolution.
Scope
--overwriteor similar flag to explicitly resolve conflicts🤖 Generated with Claude Code