Menu
Launch worktree-scoped local services for issue implementation when a monorepo skill requires database dependencies.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | docker-compose-launch |
| description | Launch worktree-scoped local services for issue implementation when a monorepo skill requires database dependencies. |
Use this skill only when the selected implementation workflow explicitly needs local services before app startup, migrations, or tests can run. Keep all service startup scoped to the assigned worktree and treat Docker Compose as a reusable helper for local implementation and test dependencies only.
The parent implementation skill should pass or infer this contract before acting:
required: true or falseworktree_path: absolute path to the assigned worktreeservice_types: one or more of mysql, mariadb, postgres, or mongodbreason: short explanation of which app, package, migration, or test command needs the servicespreferred_mechanism: repository-native compose file, repo script, or fallback compose generationIf required is false, return status: not_needed and do nothing else.
docker-compose.yml, docker-compose.yaml, compose.yml, or compose.yaml files before generating new files.Return a concise structured summary using these fields:
status: ready, not_needed, or failedservices: services that were started or detectedmechanism: repo_compose, repo_script, or generated_fallbackcommands: startup, readiness, and teardown commandsconnection: host, port, database, username, URL, or env hints when availablecleanup: explicit stop command, or noneartifacts: compose files or env files created or reusednotes: concise caveats or follow-up stepsHelp a human author write an implementation-ready GitHub issue that Vigilante can execute reliably.
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Bazel-based monorepo. Use the provided worktree, respect repository instructions, comment on the issue as work progresses, and report failures back to GitHub.
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Bazel monorepo.
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Docker-focused repository with Dockerfile best practices, image hardening, and secret-safe build guidance.
Implement a GitHub issue end-to-end when Vigilante dispatches work for a .NET/C# repository with analyzer, test, and security guidance.
Implement a GitHub issue end-to-end when Vigilante dispatches work for a repository with GitHub Actions workflows, applying workflow hardening, pinned actions, and secret-safe automation practices.