x-setup-stack
Sets up the local development environment including container orchestrator, database, and build tools.
- License 许可
- MIT
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- x-setup-stack
- description
- Sets up the local development environment including container orchestrator, database, and build tools.
- allowed-tools
- Bash, Read, Write
- argument-hint
- [--start | --stop | --status | --build]
- user-invocable
- true
- requires-capabilities
- []
02 资源文件 1
- 参考文档README.md1.5 KB
03 SKILL.md 正文
Global Output Policy
- Language: English ONLY.
- Tone: Technical, Direct, and Concise.
- Efficiency: Remove all conversational fillers and greetings to save tokens.
Skill: Dev Environment Setup
Purpose
Manage the local development environment lifecycle. Handle starting/stopping the container orchestrator ({{ORCHESTRATOR}}), provisioning the database ({{DB_TYPE}}), building the application, and verifying health checks.
Activation Condition
Include this skill when orchestrator is not "none" in the project configuration.
Triggers
/setup-environment --start-- start orchestrator, build, deploy, and set up networking/setup-environment --stop-- stop services, tear down containers, and clean up/setup-environment --status-- show running services and health check results/setup-environment --build-- rebuild application image and restart services
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
--start |
Flag | No | false | Start orchestrator, build image, deploy, set up networking |
--stop |
Flag | No | false | Stop services, tear down containers, clean up |
--status |
Flag | No | false | Show running services, pods/containers, health check results |
--build |
Flag | No | false | Rebuild application image and restart services |
Prerequisites
- {{ORCHESTRATOR}} installed and accessible in PATH
- {{DB_TYPE}} client tools available (optional, for manual queries)
- {{BUILD_TOOL}} installed (for application builds)
- Container runtime (Docker or Podman) running
Workflow
Step 1 — Verify Prerequisites
Check that required tools are installed:
- Run
whichorcommand -vfor each required tool - Verify container runtime is running (
docker infoorpodman info) - Report missing tools with installation instructions
Step 2 — Execute Requested Operation
--start:
- Start {{ORCHESTRATOR}} (e.g.,
minikube start,docker-compose up -d) - Wait for orchestrator to be ready
- Build application:
{{BUILD_COMMAND}} - Build container image
- Deploy application and dependencies ({{DB_TYPE}}, etc.)
- Wait for all services to be healthy
- Set up port-forwarding or networking as needed
--stop:
- Stop port-forwarding / networking
- Tear down application and dependencies
- Stop {{ORCHESTRATOR}} if applicable
--status:
- Show orchestrator status
- List running services/pods/containers
- Check health endpoints
- Report database connectivity
--build:
- Rebuild application:
{{BUILD_COMMAND}} - Rebuild container image
- Rolling restart / redeploy
- Wait for health checks to pass
Step 3 — Report Status
After execution:
- If successful: show access URLs (API, health, docs)
- If failed: show error message and suggested fix
Helm Mode (when infrastructure.templating == helm)
--start:
- Verify prerequisites: helm, kubectl
- Build application:
{{BUILD_COMMAND}} - Build container image:
docker build -t {{PROJECT_NAME}}:dev . - Install/upgrade chart:
helm upgrade --install {{PROJECT_NAME}} ./chart -f chart/values-dev.yaml --wait --timeout 120s - Wait for pods ready:
kubectl wait --for=condition=ready pod -l app={{PROJECT_NAME}} --timeout=120s - Port-forward:
kubectl port-forward svc/{{PROJECT_NAME}} {{PORT}}:{{PORT}}
--stop:
- Stop port-forward
- Uninstall chart:
helm uninstall {{PROJECT_NAME}}
--build:
- Build application
- Rebuild image
- Upgrade chart:
helm upgrade {{PROJECT_NAME}} ./chart -f chart/values-dev.yaml --wait
--status:
helm list(show installed charts)helm status {{PROJECT_NAME}}kubectl get pods -l app={{PROJECT_NAME}}- Health check:
curl -s http://localhost:{{PORT}}/health
Related Files
scripts/dev-setup.sh-- Main setup script (if exists)- Container orchestration manifests (k8s/, docker-compose.yml)
- Helm chart directory (chart/)
- Application configuration files
Error Handling
| Scenario | Action |
|---|---|
| Orchestrator won't start | Report container runtime not running, suggest starting Docker/Podman first |
| Service CrashLoop | Report application error, suggest checking application logs |
| Image not found | Suggest running with --build flag |
| Port conflict | Report port already in use, suggest stopping conflicting service or changing port |
| Health check timeout | Suggest waiting 30s then checking logs |
| DB connection error | Report database not ready, suggest checking database container logs |
04 同仓库更多 Skills
x-parallel-eval
Detects and classifies file-collision risks between work units (tasks, stories, or epic phases) before parallel execution. Reads ## File Footprint blocks produced by x-task-plan / x-story-plan, applies the parallelism-heuristics knowledge pack (hard / regen / soft categories + hotspot overrides), and emits a collision matrix + serialization recommendation in Markdown (default) or JSON.
parallelism-heuristics
Canonical catalog of file-collision heuristics for parallel task, story, and epic execution. Defines the File Footprint block format, the three Conflict Categories (hard / regen / soft), a hotspot list of high-contention paths, and the degrade-with-warning policy. Consumed by x-task-plan, x-story-plan, x-epic-map, x-parallel-eval, and x-dev-*-implement.
x-watch-pr-ci
Polls a PR's CI checks and Copilot review status, blocking until checks complete or timeout. Returns one of 8 stable exit codes (SUCCESS=0, CI_PENDING_PROCEED=10, CI_FAILED=20, TIMEOUT=30, PR_ALREADY_MERGED=40, NO_CI_CONFIGURED=50, PR_CLOSED=60, PR_NOT_FOUND=70). Writes a versioned state-file for session resume.
x-validate-docs
Documentation freshness gate: validates 6 dimensions (readme, api-specs, grpc-proto, adr, skill-docs, system-architecture) against code changes in a PR. Stack-aware — only validates targets declared/auto-detected from ProjectConfig.documentation.targets. Returns exit non-zero on staleness; produces structured report.
x-update-system-architecture
Incrementally updates docs/architecture/system.md after an epic completes. Appends new entries to the Decision Log (§11) using x-internal-write-report --append (dedup by ## ID: marker) and surgically inserts component/integration changes into sections 1-10 via Edit. Idempotent: re-running with the same epic produces a byte-identical system.md.
x-update-architecture
Incrementally updates the service architecture document with changes from architecture plans. Adds new components, integrations, flows, and ADR references without rewriting existing content. Use after implementation to keep architecture documentation current.