メニュー
Standardize a single scripts/setup.sh across Cloud-Neutral Toolkit repos (curl | bash), with safe cloning, dependency install, and next-step printing. Use when adding or updating setup.sh in any repo.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when a change must be made in an upstream repo that is mirrored into this control repo as a sibling checkout. Covers the required sequence: fix and push the upstream repo first, then verify the control repo references the pushed upstream commit, then commit and push the control-plane metadata change.
Use when a user asks to detect secrets in git commit history, clean tracked sensitive data, rewrite history with git-filter-repo, or verify cleanup with gitleaks. Covers gitleaks detect -v, replacement mapping, path removal, ref inventory, history rewrites, force-push planning, and post-cleanup coordination.
Use when Codex App with GPT 5.4 should act as the chief engineer and dispatch low-cost or isolated sub-tasks to ollama, opencode, or gemini CLIs instead of doing all execution itself. Best for migration verification, batch checks, document fixes, and controlled multi-model delegation.
Execute and verify the lightweight single-VPS migration path for accounts + rag-server + APISIX standalone + shared stunnel-client. Use for cheap-model test runs, preview verification, and Docker Compose smoke checks.
Use when Codex or another manager needs to hand off a concrete subtask to opencode, ollama, or gemini through scripts/orchestration/run_worker.sh. Defines the worker execution contract, prompt shape, handoff rules, and fallback behavior.
Comprehensive guide for managing the Cloud Neutral Toolkit, including environments, deployment, and security standards.
| name | unified-setup-sh |
| description | Standardize a single scripts/setup.sh across Cloud-Neutral Toolkit repos (curl | bash), with safe cloning, dependency install, and next-step printing. Use when adding or updating setup.sh in any repo. |
Provide one consistent scripts/setup.sh pattern that can be copied into any repo so users can run:
curl -fsSL "https://raw.githubusercontent.com/cloud-neutral-toolkit/<repo>/main/scripts/setup.sh?$(date +%s)" | bash -s -- <repo>
.env from .env.example only.rm -rf, no system package installs).scripts/setup.sh using the template: assets/setup.sh.chmod +x scripts/setup.sh).README.md with a copy/paste snippet for curl-based install.The template supports (auto-detected):
package.json (uses corepack enable if present, runs yarn install)go.mod (runs go mod download)Optional hooks (if present, run after deps):
scripts/post-setup.shCopy skills/unified-setup-sh/assets/setup.sh into <target-repo>/scripts/setup.sh.
If you need repo-specific parameters, add them behind -- and document in README:
curl -fsSL ".../setup.sh?$(date +%s)" | bash -s -- <repo> -- --ref main --dir <dir>
If the setup flow requires secrets later (deploy/apply), only document secret names in README and reference skills/env-secrets-governance/SKILL.md.