docs(plugin-spec): limit plugin PR scope to required files#79
Open
stephancill wants to merge 1 commit into
Open
docs(plugin-spec): limit plugin PR scope to required files#79stephancill wants to merge 1 commit into
stephancill wants to merge 1 commit into
Conversation
Collaborator
🟡 Heimdall Review Status
|
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
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.
What
Adds a Contribution Scope section to the plugin spec and marks the registry/inventory tables as maintainer-managed, so a plugin PR's diff is limited to the files actually required.
A plugin contribution should change only:
skills/base-mcp/plugins/<slug>.md, andIt should not edit the
SKILL.mdplugins table (the registry), the Integration Types Examples column, or the Existing Plugin Conformance table/count — maintainers update those when a plugin is accepted.Why
The spec currently displays the registry and the Existing Plugin Conformance table inline without saying who owns them, so contributors infer they should add themselves. In practice most in-flight plugin PRs add their own
SKILL.mdrow and a conformance-table entry (and bump the plugin count). This:Making the scope explicit (and labelling those tables maintainer-managed) prevents the conflicts and keeps review focused on the plugin file itself.
Changes
## Contribution Scopesection under "How to Author a New Plugin".Docs-only; no plugin or runtime behavior changes.