Repository navigation
docs: separate public plugin onboarding from maintainer procedures - #4
Conversation
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fd9f133531
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
|
@codex review |
|
Codex Review: Didn't find any major issues. Hooray! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
|
@codex review |
|
Codex Review: Didn't find any major issues. Keep it up! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
What changed
Why
Customer installation instructions should not contain internal operating procedures. Public documentation also needs to reflect the available OpenAI plugin without implying that a repository rename automatically updates an approved directory listing.
How it was tested
python3 -m unittest discover -s tests -v: passed, covering allowed production configuration and rejection/redaction of credential-like material, non-production hosts and internal references.python3 scripts/build.py --check: passed; generated package skills unchanged.python3 scripts/validate.py: passed.claude plugin validate packages/claude --strict: passed; the existing optional icon warning remains. Privacy policy is now discoverable from the README.claude plugin validate .: passed.git diff --check: passed.No plugin manifests, skills, MCP configuration, authentication behavior or runtime services are changed. No release tag, directory publication or deployment was performed. The documentation guard is a regression check, not a complete secret-history audit.
Deviations from team standards
None.