refactor: Move plugin.json-s to a common place#63
Conversation
83e2891 to
397f250
Compare
We need this redundancy as symlinks might not work correctly on Windows
d819429 to
3318edc
Compare
|
An example plugin with |
|
Shouldn't we use https://docs.github.com/en/copilot/reference/copilot-cli-reference/cli-plugin-reference as the source of truth for Copilot plugins? |
Do you mean the According to what we provide in Am I missing something else? Edit: I have udpated the description to link also to the GitHub CoPilot |
|
No, I just noted that we should rather use the official tool documentation than a community-driven project for referencing the expected format of plugins. |
|
Are you sure that we don't need a file |
Adjust plugin repo to support more coding agents.
With this PR we target GitHub CoPilot: #38
plugins/*/plugin.jsonnow has askillsproperty where the skills are listed.According to awesome-copilot's GUIDELINES, they follow the Claude plugin schema where
skillsare listed. Also, many of the project inside awesome-copilot's repo have this property set.GitHub CoPilot Plugin reference also lists this property: https://docs.github.com/en/copilot/reference/copilot-cli-reference/cli-plugin-reference
JIRA: CPOUI5FOUNDATION-1240