docs(sites): move the experimental sites reference and skill notes in… - #215
Conversation
…to the sites folder
|
@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. |
Greptile SummaryThis PR moves experimental Sites documentation and agent-reference notes into the Sites command folder and removes Sites from the shipped CLI skill.
Confidence Score: 4/5The documentation relocation is otherwise coherent, but the explicit repository requirement must be satisfied by removing static-site work from the installed skill’s selection description before merging. The installed skill no longer contains Sites guidance, yet its frontmatter still advertises static-site hosting and deployment requests, creating an inconsistent routing signal and leaving the experimental namespace only partially removed. Files Needing Attention: skills/bunny-cli/SKILL.md
|
| Filename | Overview |
|---|---|
| skills/bunny-cli/SKILL.md | Removes Sites instructions and routing but retains static-site work in the skill-selection description. |
| packages/cli/src/commands/skills/content.ts | Removes Sites from the embedded skill and generated AGENTS.md section. |
| packages/cli/src/commands/skills/content.test.ts | Extends the experimental-namespace exclusion test to the exact bunny sites command text. |
| packages/cli/src/commands/sites/SITES.md | Relocates the experimental Sites command reference from the package README without substantive content changes. |
| packages/cli/src/commands/sites/skill-reference.md | Parks the former installed Sites reference beside the experimental command implementation. |
Reviews (1): Last reviewed commit: "docs(sites): move the experimental sites..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| --- | ||
| name: bunny-cli | ||
| description: Manage bunny.net resources from the command line (databases, DNS, Edge Storage, Edge Scripts, static sites, sandboxes, authentication, and raw API requests) and query a Bunny Database from application code with `@bunny.net/database-client`. Use when working with bunny.net (pullzones, DNS zones/records, databases, Edge Storage zones and files, Edge Scripts, Magic Containers, static-site hosting/deploys, cloud sandboxes), invoking the `bunny` CLI, or making authenticated API calls to api.bunny.net. | ||
| description: Manage bunny.net resources from the command line (databases, DNS, Edge Storage, Edge Scripts, sandboxes, authentication, and raw API requests) and query a Bunny Database from application code with `@bunny.net/database-client`. Use when working with bunny.net (pullzones, DNS zones/records, databases, Edge Storage zones and files, Edge Scripts, Magic Containers, static-site hosting/deploys, cloud sandboxes), invoking the `bunny` CLI, or making authenticated API calls to api.bunny.net. |
There was a problem hiding this comment.
The frontmatter still tells agents to use this skill for static-site hosting and deployments, but this change removes every Sites example and reference from the installed skill. A static-site request can therefore select a skill that provides no route to the relevant instructions. This violates the repository directive that experimental namespaces, including Sites, must stay out of the skill until they graduate, so the requirement must be satisfied before merging.
| description: Manage bunny.net resources from the command line (databases, DNS, Edge Storage, Edge Scripts, sandboxes, authentication, and raw API requests) and query a Bunny Database from application code with `@bunny.net/database-client`. Use when working with bunny.net (pullzones, DNS zones/records, databases, Edge Storage zones and files, Edge Scripts, Magic Containers, static-site hosting/deploys, cloud sandboxes), invoking the `bunny` CLI, or making authenticated API calls to api.bunny.net. | |
| description: Manage bunny.net resources from the command line (databases, DNS, Edge Storage, Edge Scripts, sandboxes, authentication, and raw API requests) and query a Bunny Database from application code with `@bunny.net/database-client`. Use when working with bunny.net (pullzones, DNS zones/records, databases, Edge Storage zones and files, Edge Scripts, Magic Containers, cloud sandboxes), invoking the `bunny` CLI, or making authenticated API calls to api.bunny.net. |
Context Used: AGENTS.md (source)
![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: 93c27ced17
ℹ️ 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".
| --- | ||
| name: bunny-cli | ||
| description: Manage bunny.net resources from the command line (databases, DNS, Edge Storage, Edge Scripts, static sites, sandboxes, authentication, and raw API requests) and query a Bunny Database from application code with `@bunny.net/database-client`. Use when working with bunny.net (pullzones, DNS zones/records, databases, Edge Storage zones and files, Edge Scripts, Magic Containers, static-site hosting/deploys, cloud sandboxes), invoking the `bunny` CLI, or making authenticated API calls to api.bunny.net. | ||
| description: Manage bunny.net resources from the command line (databases, DNS, Edge Storage, Edge Scripts, sandboxes, authentication, and raw API requests) and query a Bunny Database from application code with `@bunny.net/database-client`. Use when working with bunny.net (pullzones, DNS zones/records, databases, Edge Storage zones and files, Edge Scripts, Magic Containers, static-site hosting/deploys, cloud sandboxes), invoking the `bunny` CLI, or making authenticated API calls to api.bunny.net. |
There was a problem hiding this comment.
The frontmatter still advertises static-site hosting/deploys, so requests about static sites can activate the installed skill even though this commit removes the sites reference and bunny sites is hidden from command discovery. In that scenario the agent is routed to a skill that no longer explains the experimental command, defeating the intended exclusion; remove this remaining trigger until the namespace graduates.
AGENTS.md reference: AGENTS.md:L289-L289
Useful? React with 👍 / 👎.
|
|
||
| /** The shipped bunny-cli skill, embedded at bundle time from skills/bunny-cli/. */ | ||
| // Experimental namespaces (apps, registries) stay out of the skill until they stabilize. | ||
| // Experimental namespaces (apps, registries, sites) stay out of the skill until they stabilize. |
There was a problem hiding this comment.
For anyone who installed the previous skill and then runs bunny skills install/update, removing references/sites.md from this manifest does not remove the installed copy: writeSkillFiles() deletes only the SKILL.md sentinel and overwrites the entries still present in skill.files. The stale sites reference therefore remains under the project or global skill roots after a successful refresh, so existing installations do not actually exclude the experimental namespace; reconcile the destination directory or explicitly remove this retired reference during the update.
AGENTS.md reference: AGENTS.md:L289-L289
Useful? React with 👍 / 👎.
3 participants
…to the sites folder