manage-infra
Automates starting, stopping, and resetting Docker-based infrastructure.
Install
mkdir -p .claude/skills/manage-infra && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14176" && unzip -o skill.zip -d .claude/skills/manage-infra && rm skill.zipInstalls to .claude/skills/manage-infra
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Starts or stops the Docker Compose infrastructure (Postgres 17).Key capabilities
- →Start Docker Compose services
- →Stop Docker Compose services
- →Reset Docker Compose services by removing volumes
- →Verify Docker Compose container status
- →View Docker Compose service logs
How it works
The skill executes predefined Docker Compose commands to manage a Postgres 17 infrastructure.
Inputs & outputs
When to use manage-infra
- →Start the database
- →Stop and reset local infrastructure
- →Check service logs
About this skill
Skill: Manage Infrastructure
Visual Studio Code Tasks
- To Start: Run the VS Code task:
"Start Docker Compose".- This builds and starts containers in detached mode using
./docker/docker-compose.yaml.
- This builds and starts containers in detached mode using
- To Stop: Run the VS Code task:
"Stop Docker Compose". - To Reset (Wipe Data): Run the VS Code task:
"Stop & Remove Volumes".
Docker Compose
From the project root directory:
-
To Start: Run the Docker Compose command:
docker compose -f ./docker/docker-compose.yaml up -d -
To Stop: Run the Docker Compose command:
docker compose -f ./docker/docker-compose.yaml down -
To Reset (Wipe Data): Run the Docker Compose command:
docker compose -f ./docker/docker-compose.yaml down -v
Verification
-
Make sure the arch-stats container started successfully before starting the Backend or Frontend servers:
docker compose -f ./docker/docker-compose.yaml ps --allThis means:
- arch-stats-db-1 is healthy
- arch-stats-migrations-1 exited successfully (exit code 0)
Logs
-
To View Logs: Run the Docker Compose command:
docker compose -f ./docker/docker-compose.yaml logs # or docker compose -f ./docker/docker-compose.yaml logs db # or docker compose -f ./docker/docker-compose.yaml logs migrations
When not to use it
- →When Docker Compose is not used for infrastructure management
- →When managing infrastructure that is not Postgres 17
Limitations
- →The skill is specific to Docker Compose infrastructure.
- →The skill is configured for Postgres 17.
- →The skill relies on a specific `docker-compose.yaml` file path.
How it compares
This skill automates common Docker Compose operations, providing a standardized way to manage the infrastructure compared to manually typing commands.
Compared to similar skills
manage-infra side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| manage-infra (this skill) | 0 | 6mo | Review | Beginner |
| supabase-local-dev-loop | 0 | 29d | Caution | Beginner |
| supabase-multi-env-setup | 1 | 29d | Review | Advanced |
| fly-io-deployer | 0 | 3mo | Caution | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
supabase-local-dev-loop
jeremylongshore
Configure Supabase local development with hot reload and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with Supabase. Trigger with phrases like "supabase dev setup", "supabase local development", "supabase dev environment", "develop with supabase".
supabase-multi-env-setup
jeremylongshore
Configure Supabase across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Supabase configurations. Trigger with phrases like "supabase environments", "supabase staging", "supabase dev prod", "supabase environment setup", "supabase config by env".
fly-io-deployer
LeoYeAI
Deploy and operate Node, Python, Go, Rust, Elixir, and Docker apps on Fly.io with production-grade fly.toml authoring, Machines API orchestration, region selection (latency vs sovereignty vs egress), Fly Postgres clustering, LiteFS for SQLite replication, Upstash Redis bindings, Tigris object storag
dust-hive
dust-tt
Information about dust-hive, a CLI tool for running multiple isolated Dust development environments. ALWAYS enable this skill when the working directory is under ~/dust-hive/. Use for understanding port allocation, running tests, and working with the environment.
test-with-postgres
storj
Run unit tests that require PostgreSQL. Use this skill when the user wants to run tests with PostgreSQL database backend. Automatically handles checking for and configuring a PostgreSQL Docker container.
local-env
dailydotdev
Local environment management - run SQL queries, set up fake payments, reset test data. Use when the user needs help with local database operations or test data setup.