メニュー
Rules for safe development on this live, published extension
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
How to bump package versions in kuskus — required before merging any PR that touches a package
How to update SHA-pinned GitHub Actions in kuskus workflows
Opening and reviewing PRs in the kuskus repo
Master branch protection rules, bypass policy, and how to modify when needed
Triage and label issues in the kuskus repo
How automated publishing works in kuskus
| name | Kuskus-Safe-Development |
| description | Rules for safe development on this live, published extension |
master. Always use a branch and PR.vsce publish manually. CI handles publishing.*-publish.yml workflows without understanding them fully. They are production infrastructure.Every merge to master triggers a publish to the VS Code Marketplace. There is no staging. A bad merge ships immediately.
npm test in kusto-language-server runs an e2e suite that requires a VS Code extension host. It does not run in CI. Use npm run lint and npm run vscode:prepublish to catch issues before opening a PR.