fix!: disambiguate references in built skills (#70)#71
Merged
zachdaniel merged 1 commit intoash-project:mainfrom Apr 16, 2026
Merged
Conversation
Contributor
|
Not a breaking change, we can remove that from the commit message 😄 |
When a built skill bundles multiple packages (e.g. :ash + :ash_oban) via
`skills: [build: [...]]`, two problems surfaced:
1. On-disk collision: both packages ship `usage-rules/multitenancy.md`.
Both were written to `references/multitenancy.md` — silent overwrite.
2. Rendering ambiguity: the "Additional References" section listed
`- [multitenancy](references/multitenancy.md)` once with no way to tell
which library it came from.
Now reference files live under per-package subdirectories
(`references/<pkg>/<name>.md`) and the section groups them under
H3 subsections per package:
## Additional References
### ash
- [ash](references/ash/ash.md)
- [multitenancy](references/ash/multitenancy.md)
### ash_oban
- [ash_oban](references/ash_oban/ash_oban.md)
- [multitenancy](references/ash_oban/multitenancy.md)
Stale flat-layout files from prior syncs are cleaned up automatically,
so upgrading users don't need to do anything.
Fixes: ash-project#70
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
Munksgaard
force-pushed
the
fix/disambiguate-built-skill-references
branch
from
5b949c6 to
ec82281
Compare
Contributor
Author
Done! |
zachdaniel
approved these changes
Apr 15, 2026
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
2 participants
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.
When a built skill bundles multiple packages (e.g. :ash + :ash_oban) via
skills: [build: [...]], two problems surfaced:usage-rules/multitenancy.md. Both were written toreferences/multitenancy.md— silent overwrite.- [multitenancy](references/multitenancy.md)once with no way to tell which library it came from.Now reference files live under per-package subdirectories (
references/<pkg>/<name>.md) and the section groups them under H3 subsections per package:Stale flat-layout files from prior syncs are cleaned up automatically, so upgrading users don't need to do anything.
Fixes: #70
Contributor checklist
Leave anything that you believe does not apply unchecked.