doc: split local-dev skill into server management and bai-cli usage#10795
doc: split local-dev skill into server management and bai-cli usage#10795HyeockJinKim merged 2 commits intomainfrom
Conversation
Separate the local-dev skill into two focused skills: - local-dev: server management only (./dev start/stop/restart) - bai-cli: v2 CLI usage guide with inline entity-command reference Add situation-based skill mapping to CLAUDE.md and enforce /bai-cli skill loading before any ./bai command execution. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Splits the previous /local-dev skill into a narrower server-management guide and a new /bai-cli skill that documents v2 CLI usage, plus updates top-level guidance to require loading /bai-cli before running ./bai.
Changes:
- Refactors
/local-devto cover only./devservice management and troubleshooting. - Adds new
/bai-cliskill with v1→v2 terminology mapping and an entity-command quick reference. - Updates
CLAUDE.mdand the skills README to reflect the new skill split and usage flow.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 9 comments.
Show a summary per file
| File | Description |
|---|---|
| changes/10795.doc.md | Adds a changelog entry documenting the skill split. |
| CLAUDE.md | Updates skill selection guidance and enforces /bai-cli before ./bai. |
| .claude/skills/local-dev/SKILL.md | Removes CLI content; keeps local server/service management guidance only. |
| .claude/skills/bai-cli/entity-reference.md | Introduces a standalone entity-command quick reference for ./bai. |
| .claude/skills/bai-cli/SKILL.md | Adds comprehensive ./bai v2 CLI usage guide with inline entity reference. |
| .claude/skills/README.md | Documents the new /bai-cli skill and updates recommended flows. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - **service-catalog**: admin(search, create, update, delete) | ||
| - **runtime-variant**: user(search, get) | admin(search, create, update, delete) | ||
| - **runtime-variant-preset**: user(search, get) | admin(search, create, update, delete) | ||
| - **scheduling-history**: sub: session(search, search-scoped), deployment(search, search-scoped), route(search, search-scoped) |
There was a problem hiding this comment.
The scheduling-history entry is duplicated in the same document. Remove one of the duplicates to avoid confusion and reduce drift in future edits.
| - **scheduling-history**: sub: session(search, search-scoped), deployment(search, search-scoped), route(search, search-scoped) |
| ## Monitoring & Audit | ||
|
|
||
| - **audit-log**: user(search) | admin(search) | ||
| - **scheduling-history**: sub: session(search, search-scoped), deployment(search, search-scoped), route(search, search-scoped) |
There was a problem hiding this comment.
The scheduling-history entry is duplicated in the same document. Remove one of the duplicates to avoid confusion and reduce drift in future edits.
| - **scheduling-history**: sub: session(search, search-scoped), deployment(search, search-scoped), route(search, search-scoped) |
| - **service-catalog**: admin(search, create, update, delete) | ||
| - **runtime-variant**: user(search, get) | admin(search, create, update, delete) | ||
| - **runtime-variant-preset**: user(search, get) | admin(search, create, update, delete) | ||
| - **scheduling-history**: sub: session(search, search-scoped), deployment(search, search-scoped), route(search, search-scoped) |
There was a problem hiding this comment.
The scheduling-history entry appears twice (under both 'Compute & Serving' and 'Monitoring & Audit'). Pick a single section (likely Monitoring & Audit) and remove the duplicate to keep the reference unambiguous.
| - **scheduling-history**: sub: session(search, search-scoped), deployment(search, search-scoped), route(search, search-scoped) |
| ### Monitoring & Audit | ||
|
|
||
| - **audit-log**: user(search) | admin(search) | ||
| - **scheduling-history**: sub: session(search, search-scoped), deployment(search, search-scoped), route(search, search-scoped) |
There was a problem hiding this comment.
The scheduling-history entry appears twice (under both 'Compute & Serving' and 'Monitoring & Audit'). Pick a single section (likely Monitoring & Audit) and remove the duplicate to keep the reference unambiguous.
| - **scheduling-history**: sub: session(search, search-scoped), deployment(search, search-scoped), route(search, search-scoped) |
| Syntax: `./bai [admin|my] {entity} [{sub-entity}] {command} [options]` | ||
|
|
There was a problem hiding this comment.
The reference tables use user(...) to mean the default (no prefix) command set, but the syntax line only mentions [admin|my] and doesn't explain how 'user' maps to the actual CLI invocation. Clarify that user(...) corresponds to running ./bai {entity} ... (no prefix), and consider adjusting the syntax line to explicitly mention the default/no-prefix case.
| Syntax: `./bai [admin|my] {entity} [{sub-entity}] {command} [options]` | |
| Syntax: `./bai [admin|my] {entity} [{sub-entity}] {command} [options]` or `./bai {entity} [{sub-entity}] {command} [options]` | |
| In the reference tables below, `user(...)` means the default command set with no prefix, i.e. `./bai {entity} [{sub-entity}] {command} [options]`. |
| - **domain**: user(get) | admin(search, create, update, delete) | ||
| - **user**: user(get, create, update, delete, search) | admin(create, delete) |
There was a problem hiding this comment.
The reference tables use user(...) to mean the default (no prefix) command set, but the syntax line only mentions [admin|my] and doesn't explain how 'user' maps to the actual CLI invocation. Clarify that user(...) corresponds to running ./bai {entity} ... (no prefix), and consider adjusting the syntax line to explicitly mention the default/no-prefix case.
| ## Entity-Command Reference | ||
|
|
||
| Syntax: `./bai [admin|my] {entity} [{sub-entity}] {command} [options]` |
There was a problem hiding this comment.
The entity-command reference is duplicated in two places: inline in this skill and also in .claude/skills/bai-cli/entity-reference.md. Keeping two copies of the same reference will likely drift over time; prefer a single source of truth (either keep it inline and delete the standalone file, or keep the standalone file and link to it from the skill).
|
|
||
| ### Core | ||
|
|
||
| - **domain**: user(get) | admin(search, create, update, delete) |
There was a problem hiding this comment.
The entity-command reference is duplicated in two places: inline in this skill and also in .claude/skills/bai-cli/entity-reference.md. Keeping two copies of the same reference will likely drift over time; prefer a single source of truth (either keep it inline and delete the standalone file, or keep the standalone file and link to it from the skill).
| - **notification**: sub: channel(search, get, delete), rule(search, get, delete) | ||
| - **prometheus-query-definition**: user(search, get, create, update, execute, delete) | admin(search, create, update, delete) | ||
| - **app-config**: user(get-domain, delete-domain, get-user, delete-user, get-merged) | admin(create, update, delete) | ||
| - **export**: admin(list, request, purge) | my(list, request, purge) |
There was a problem hiding this comment.
The entity-command reference is duplicated in two places: inline in this skill and also in .claude/skills/bai-cli/entity-reference.md. Keeping two copies of the same reference will likely drift over time; prefer a single source of truth (either keep it inline and delete the standalone file, or keep the standalone file and link to it from the skill).
Summary
local-devskill into two focused skills:local-dev(server management only) andbai-cli(v2 CLI usage guide)bai-cliskill with v1→v2 terminology mapping/bai-cliskill loading before any./baicommandTest plan
/bai-cliskill loads correctly and entity-reference is inline/local-devskill contains only server management content/bai-clibefore running./baicommandsgroupvsproject) confusion after fix🤖 Generated with Claude Code