メニュー
Generate GitHub Actions CI/CD workflow YAML for a new deployment environment. Use when setting up a new environment that needs a GitHub Actions pipeline for building Docker images and deploying to Kubernetes (Azure AKS or GCP GKE). Can also be called by the setup_new_deployment parent skill.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | generate_github_actions_file |
| description | Generate GitHub Actions CI/CD workflow YAML for a new deployment environment. Use when setting up a new environment that needs a GitHub Actions pipeline for building Docker images and deploying to Kubernetes (Azure AKS or GCP GKE). Can also be called by the setup_new_deployment parent skill. |
Generate a GitHub Actions CI/CD workflow for a new Tone deployment environment.
Only ENV_NAME is required. All other values are derived:
| Value | Convention |
|---|---|
BRANCH_NAME | Same as ENV_NAME |
ENV_NAME_TITLE | Title-cased ENV_NAME (e.g., Production CI/CD) |
DOCKER_REPO | developer390/tone |
DOCKER_TAG_PREFIX | {ENV_NAME}-latest |
KUBE_CONFIG_SECRET | {ENV_NAME_UPPER}_KUBE_CONFIG_JSON |
RESOURCE_PREFIX | {ENV_NAME}- (empty for dev) |
CLOUD_PROVIDER | azure (default) |
Single file: .github/workflows/{ENV_NAME}.yaml
references/azure-workflow.md template.CLOUD_PROVIDER=gcp, read references/gcp-workflow.md instead.{PLACEHOLDER} values..github/workflows/{ENV_NAME}.yaml.The workflow references api/ and call/ subdirectories:
# Manifests are under build/kubernetes/{ENV_NAME}/api/ and call/
kubectl apply -f build/kubernetes/{ENV_NAME}/api/deployment.yaml
kubectl apply -f build/kubernetes/{ENV_NAME}/call/deployment.yaml
Use this skill when the user asks to "review my changes", "code review", "review before commit", "/code-review", or wants SOLID, security, performance, accessibility, or error handling analysis on current git changes. Accepts an optional base branch argument (defaults to main).
Generates feature documentation for a Next.js page by analyzing component source, service imports, Jotai atoms, and navigation paths. Output placed in e2e/ux_flow_docs/<page-name>.md and consumed by /generate-tests for comprehensive test coverage.
Generates a new Playwright e2e spec file by reading a page component's source code, then runs it. Use when a page has NO existing spec file and you need to create one from scratch.
Skill for the Test-cases area of tone. 250 symbols across 60 files.
Generate and maintain pytest test cases for FastAPI endpoints by reading the APIs.md documentation and tracing actual controller/service code. Creates one test file per controller with comprehensive coverage (success, failure, validation, auth, edge cases). Use this skill when the user asks to generate tests, create test cases, write API tests, add pytest coverage, or mentions "test my APIs". Also triggers on "generate tests", "write test cases", "add test coverage", or "pytest for my endpoints".
Creates a new shared UI component using shadcn/ui with the project's theme. Handles shadcn setup verification, theme token mapping, and generates production-ready components following project conventions.