[docs] Update documentation for features from 2026-04-04#569
Closed
danielmeppiel wants to merge 1 commit into
Closed
[docs] Update documentation for features from 2026-04-04#569danielmeppiel wants to merge 1 commit into
danielmeppiel wants to merge 1 commit into
Conversation
- Add CHANGELOG.md entry under [Unreleased] Fixed for the new cross-package native skill name collision warning - Add 'Skill Name Collision Warning' troubleshooting section in docs/src/content/docs/guides/skills.md explaining the warning message and how to resolve the conflict Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
danielmeppiel
added
automation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates user documentation to reflect the newly added native skill name collision warning behavior introduced in #545, ensuring users understand what the warning means and how to resolve it.
Changes:
- Added a troubleshooting section describing the "Skill Name Collision Warning" and remediation steps.
- Added a
Fixedentry under[Unreleased]documenting the native-skill collision warning behavior.
Show a summary per file
| File | Description |
|---|---|
| docs/src/content/docs/guides/skills.md | Adds troubleshooting guidance for native skill name collisions and how to resolve them. |
| CHANGELOG.md | Documents the collision warning behavior under [Unreleased] -> Fixed. |
Copilot's findings
- Files reviewed: 2/2 changed files
- Comments generated: 1
Comment on lines
+383
to
+385
| ``` | ||
| [!] Skill 'humanizer': replaced 'org/other-package' -- remove one package to avoid this | ||
| ``` |
There was a problem hiding this comment.
The example warning message does not match the actual collision warning emitted by SkillIntegrator. Current code formats the detail as "Skill '' from '' replaced '<prev_owner>' -- remove one package to avoid this"; the docs example omits the "from ''" portion (and uses a colon), but the surrounding text says the warning names both packages. Update the example (and any related wording) so it mirrors the real message format users will see.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation Updates - 2026-04-04
This PR updates the documentation based on features merged in the last 24 hours.
Features Documented
Changes Made
CHANGELOG.mdto add aFixedentry under[Unreleased]for the cross-package native skill collision detection introduced in [fix] warn when two packages deploy a native skill with the same name #545.docs/src/content/docs/guides/skills.mdexplaining the new warning message and how users can resolve the conflict.Merged PRs Referenced
[fix] warn when two packages deploy a native skill with the same name-- when two installed packages deploy a native skill with the same leaf directory name, APM now emits a warning identifying both the incoming package and the previous owner, and tells the user to remove one to resolve the conflict. Previously the second install silently overwrote the first.Notes
No other PRs were merged in the last 24 hours. The CHANGELOG entry and troubleshooting note cover all user-facing aspects of #545.