원클릭으로
update-ticloud-cli-command
Update TiDB Cloud CLI commands. Use when adding new flags or updating existing commands.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Update TiDB Cloud CLI commands. Use when adding new flags or updating existing commands.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | update-ticloud-cli-command |
| description | Update TiDB Cloud CLI commands. Use when adding new flags or updating existing commands. |
| license | Complete terms in LICENSE.txt |
| metadata | {"author":"shiyuhang0"} |
This skill updates TiDB Cloud CLI existing commands, helping users update existing commands with production-ready code.
TiDB Cloud CLI (TiCloud CLI) is a command-line interface for interacting with TiDB Cloud, built on the Cobra library.
Key design of TiDB Cloud CLI:
Built on the Cobra library.
Uses the TiDB Cloud Open API as the client and keeps the SDK inside the project.
Every command supports both interactive and non-interactive modes.
More about TiDB Cloud CLI: references/tidbcloud-cli.md.
More about Cobra: references/cobra.md.
Must follow the workflow below:
Always prompt the user: "Do you need to add or update swagger? Please provide the swagger path if you need."
Skip this phase if user does not need.
Once in this phase, follow the guide in references/sdk.md to generate the SDK.
After SDK is generated, ask user to use go>=1.24 to run make generate-mocks manually!
The agent needs to switch to plan mode if supported. This phase can be skipped if user already provide enough informations.
The agent must ask the user for the following information during the plan phase:
Generate the plan after the user confirms all the information.
The agent must switch to agent mode in this phase. Follow the workflow below:
Update the command according to user-provided information and current command code style.
If new flags are added:
references/flag.md for the flag definition.references/ui.md for the UI design.Skip this step if the test file does not exist. Otherwise, write unit tests following references/ut.md. Then run tests with: go test -race -cover -count=1 path -v
For example, to run tests under internal/cli/serverless/branch: go test -race -cover -count=1 ./internal/cli/serverless/branch -v
Ensure all tests pass. If they do not pass, fix the implementation or the tests.