Repository navigation
docs: separate marketplace and plugin overviews from usage details - #27
Merged
Merged
Conversation
Keep the permission policy, scan limits, configuration and log reference inside the installed plugin. Give visitors capability summaries before the full contracts, and keep contributor procedures in development docs.
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.
The marketplace README mixed plugin selection with update instructions and generated-type setup. It now introduces preallow and links to the installation owner and contributor procedures.
preallow's README summarizes the judge, native approval boundaries, output scanning, configuration and limits. The complete installation, policy, settings, known gaps and log reference move to
plugins/preallow/docs/usage.md, inside the folder Claude Code installs. The relocated content is unchanged apart from its heading and prerequisite; local links and heading targets resolve.