mirror of
https://github.com/github/awesome-copilot.git
synced 2026-08-07 18:03:02 +00:00
Aaron Powell
a7fdcd5006
* feat: migrate plugins and extensions to Agent Plugins v1.0.0 spec - Add \ to all 69 curated plugin manifests - Migrate all 18 extension manifests: add \, move logo into xtensions.com.github.copilot.logo namespace, remove top-level logo and string xtensions: '.' - Update eng/validate-plugins.mjs: require \, validate namespace-keyed extensions object for canvas extensions, widen name pattern to allow dots (spec §5.5, max 64 chars) - Update eng/materialize-plugins.mjs: emit spec-clean served manifests (only spec fields: \, name, version, description, author, homepage, repository, license, keywords, extensions) - Update eng/generate-website-data.mjs: read logo from namespace with fallback to top-level logo for compatibility - Update eng/create-plugin.mjs: scaffold emits \ - Add .github/workflows/validate-plugins.yml: blocking CI for PRs touching plugins/** or extensions/** - Add spec compliance check to external plugin quality gates: non-blocking warnings with ✅/⚠️/🛑 emoji legend - Update AGENTS.md: document new extension manifest shape, add \ to plugin checklist Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8f3a88cb-e01e-4760-8125-460490dc1a76 * refactor: consolidate canvas extension plugins - Move all extension plugin manifests from extensions/<name> to plugins/<name> - Keep extensions/<name> as reusable source only - Remove standalone extension discovery from marketplace and website plugin catalogs - Auto-bundle same-name extension sources during materialization - Add build-only extensions.json references for sharing extensions across plugins - Remove x-awesome-copilot extension metadata support - Update validation and contributor documentation Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8f3a88cb-e01e-4760-8125-460490dc1a76 * feat: add canvas extension scaffolding skill - Add repo-local skill for creating canvas extension sources - Generate spec-compliant plugin manifests under plugins/ - Support registering reusable extensions with multiple plugins - Remove guidance for extension-local plugin manifests and custom fields Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8f3a88cb-e01e-4760-8125-460490dc1a76 * fix: align extension namespaces with current guidance - Use each extension ID as its manifest namespace key - Update validation and website generation to resolve extension-specific namespaces - Upsert plugin validation PR comments using the existing repository pattern Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8f3a88cb-e01e-4760-8125-460490dc1a76 * fix: use Copilot extension namespace - Adopt com.github.copilot for all canvas extension manifests - Require the namespace during validation and website generation - Update extension scaffolding guidance Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8f3a88cb-e01e-4760-8125-460490dc1a76 * docs: regenerate plugin catalog after merge Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8f3a88cb-e01e-4760-8125-460490dc1a76 * refactor(plugins): move manifests to plugin roots Use root plugin.json manifests and namespaced extension directories throughout local tooling, validation, generation, and contributor documentation. Restore materialize-plugins.mjs line breaks so the source remains readable in GitHub. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8f3a88cb-e01e-4760-8125-460490dc1a76 * feat(plugins): migrate manifests to namespaced composition Move repository composition metadata under com.github.awesome-copilot, materialize reusable extensions into the plugin extensions directory, and improve contributor and PR validation guidance. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8f3a88cb-e01e-4760-8125-460490dc1a76 * fix(validation): address plugin review findings Restore executable build scripts, validate namespaced manifests and hook directories, improve README item counts, and manage validation comments across reruns. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8f3a88cb-e01e-4760-8125-460490dc1a76 * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Copilot-Session: 8f3a88cb-e01e-4760-8125-460490dc1a76
72 lines
3.2 KiB
Markdown
72 lines
3.2 KiB
Markdown
The following instructions are only to be applied when performing a code review.
|
|
|
|
## README updates
|
|
|
|
- [ ] The new file should be added to the `docs/README.<type>.md`.
|
|
|
|
## Prompt file guide
|
|
|
|
**Only apply to files that end in `.prompt.md`**
|
|
|
|
- [ ] The prompt has markdown front matter.
|
|
- [ ] The prompt has a `agent` field specified of either `agent`, `ask`, or `Plan`.
|
|
- [ ] The prompt has a `description` field.
|
|
- [ ] The `description` field is not empty.
|
|
- [ ] The file name is lower case, with words separated by hyphens.
|
|
- [ ] Encourage the use of `tools`, but it's not required.
|
|
- [ ] Strongly encourage the use of `model` to specify the model that the prompt is optimised for.
|
|
- [ ] Strongly encourage the use of `name` to set the name for the prompt.
|
|
|
|
## Instruction file guide
|
|
|
|
**Only apply to files that end in `.instructions.md`**
|
|
|
|
- [ ] The instruction has markdown front matter.
|
|
- [ ] The instruction has a `description` field.
|
|
- [ ] The `description` field is not empty.
|
|
- [ ] The file name is lower case, with words separated by hyphens.
|
|
- [ ] The instruction has an `applyTo` field that specifies the file or files to which the instructions apply. If they wish to specify multiple file paths they should formatted like `'**.js, **.ts'`.
|
|
|
|
## Agent file guide
|
|
|
|
**Only apply to files that end in `.agent.md`**
|
|
|
|
- [ ] The agent has markdown front matter.
|
|
- [ ] The agent has a `description` field.
|
|
- [ ] The `description` field is not empty.
|
|
- [ ] The file name is lower case, with words separated by hyphens.
|
|
- [ ] Encourage the use of `tools`, but it's not required.
|
|
- [ ] Strongly encourage the use of `model` to specify the model that the agent is optimised for.
|
|
- [ ] Strongly encourage the use of `name` to set the name for the agent.
|
|
|
|
## Agent Skills guide
|
|
|
|
**Only apply to folders in the `skills/` directory**
|
|
|
|
- [ ] The skill folder contains a `SKILL.md` file.
|
|
- [ ] The SKILL.md has markdown front matter.
|
|
- [ ] The SKILL.md has a `name` field.
|
|
- [ ] The `name` field value is lowercase with words separated by hyphens.
|
|
- [ ] The `name` field matches the folder name.
|
|
- [ ] The SKILL.md has a `description` field.
|
|
- [ ] The `description` field is not empty, at least 10 characters, and maximum 1024 characters.
|
|
- [ ] The `description` field value is wrapped in single quotes.
|
|
- [ ] The folder name is lower case, with words separated by hyphens.
|
|
- [ ] Any bundled assets (scripts, templates, data files) are referenced in the SKILL.md instructions.
|
|
- [ ] Bundled assets are reasonably sized (under 5MB per file).
|
|
|
|
## Plugin guide
|
|
|
|
**Only apply to directories in the `plugins/` directory**
|
|
|
|
- [ ] The plugin directory contains a root `plugin.json` file.
|
|
- [ ] The plugin directory contains a `README.md` file.
|
|
- [ ] The plugin.json has a `name` field matching the directory name.
|
|
- [ ] The plugin.json has a `description` field.
|
|
- [ ] The `description` field is not empty.
|
|
- [ ] The directory name is lower case, with words separated by hyphens.
|
|
- [ ] If `tags` is present, it is an array of lowercase hyphenated strings.
|
|
- [ ] If `items` is present, each item has `path` and `kind` fields.
|
|
- [ ] The `kind` field value is one of: `prompt`, `agent`, `instruction`, `skill`, or `hook`.
|
|
- [ ] The plugin does not reference non-existent files.
|