skills: OpenCode's and Goose's folders are read too - #1691
Merged
Merged
Conversation
Issue #1277's day-one list names .opencode/skills and .goose/skills beside the six folders discovery already read. They are appended after .gemini, so a name held in any of the first six still owns it and the later copy is kept in the result marked shadowed, in both the project and the home scope. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> (cherry picked from commit 5d6f36f)
OpenCode keeps a person's global skills in ~/.config/opencode/skills and Goose in ~/.config/goose/skills, so the dot folders named after each tool are empty on a machine that uses them. Both are now read in the home scope only, after the shared folders and before plugin and bundled skills, so a name kept by hand anywhere earlier still owns it. A project's own .config folder is not read. The comments no longer count the folders, because the count had already drifted once. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…p them The page listed six folders. It now names .opencode/skills and .goose/skills beside them, and the two ~/.config folders that are read in the home only, so "can codeaf use my Goose skills" reaches an answer that says yes and where. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Supersedes #1409, which was stacked on #1410 and could not merge once #1410 was squashed into dev. This is its change re-cut onto current dev, plus the home folders those two tools actually use.
What changes
.opencode/skillsand.goose/skillsare read after.gemini/skills, so a name kept in any earlier folder still owns it.~/.config/opencode/skillsand~/.config/goose/skillsare read in the user scope, after the shared folders and before plugin and bundled skills. That is where OpenCode (docs) and Goose (docs) keep a person's global skills;~/.opencode/skillsand~/.goose/skillsare empty on machines that use them. A project's own.configfolder is not read.skills-from-other-tools.mdnames both tools and all four folders.Validation contract
.opencode/skillsor.goose/skillsis found in the project scope.~/.config/opencode/skillsor~/.config/goose/skillsis found in the user scope, under its own root name..config/opencode/skillsis not read.~/.claude/skills) shadows the~/.configcopy, and any project skill shadows every home one.~/.configskill is reported once.Each test fails with its folder list removed. By hand, the real binary's
/skillpicker in a throwaway home listsoc-project,goose-project,oc-globalandgoose-global; current dev lists none of them.codeaf manual "can codeaf use my goose skills"reaches the updated section.🤖 Generated with Claude Code