Refactor plugin creation instructions in CONTRIBUTING.md (#481)

Removed redundant instructions for creating a new plugin from the 'Plugin organization' section.
This commit is contained in:
Viktor Hofer
2026-03-31 13:59:08 +02:00
committed by GitHub
parent 3fff1f2573
commit 187c2e7c31
+11 -11
View File
@@ -46,7 +46,17 @@ Every plugin must have a plugin.json file in the plugin root that is linked to f
### Plugin organization
Skills are grouped into domain-specific plugins. When proposing a new skill, place it in the plugin that best matches its domain. See [README.md](README.md) for the current list of plugins.
If your skill does not fit any existing plugin, consider creating a new one. The following plugin names are reserved for future use and are good candidates for new skills in those areas:
If your skill does not fit any existing plugin, consider creating a new one.
To create a new plugin:
1. Add `plugins/<plugin-name>/plugin.json` and a `skills/` directory beneath it.
2. Add a matching entry in both `.github/plugin/marketplace.json` and `.claude-plugin/marketplace.json`. The `.claude-plugin/marketplace.json` file must remain an exact copy of `.github/plugin/marketplace.json`, so any change to one file (adding, removing, or editing a plugin entry) must be applied to the other in the same way.
3. Add a CODEOWNERS entry for the new plugin and its tests (see [Code ownership](#code-ownership)).
4. Add the plugin to the **What's Included** table in the root `README.md`.
5. Create a `tests/<plugin-name>/` directory for skill tests.
See existing plugins for the expected format.
### The `dotnet-experimental` plugin
@@ -60,16 +70,6 @@ Skills in `dotnet-experimental`:
Place experimental skills under `plugins/dotnet-experimental/skills/` with matching tests in `tests/dotnet-experimental/`.
To create a new plugin:
1. Add `plugins/<plugin-name>/plugin.json` and a `skills/` directory beneath it.
2. Add a matching entry in both `.github/plugin/marketplace.json` and `.claude-plugin/marketplace.json`. The `.claude-plugin/marketplace.json` file must remain an exact copy of `.github/plugin/marketplace.json`, so any change to one file (adding, removing, or editing a plugin entry) must be applied to the other in the same way.
3. Add a CODEOWNERS entry for the new plugin and its tests (see [Code ownership](#code-ownership)).
4. Add the plugin to the **What's Included** table in the root `README.md`.
5. Create a `tests/<plugin-name>/` directory for skill tests.
See existing plugins for the expected format.
## Before you start
- Search existing issues and pull requests to avoid duplicates.