ops-run-local
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- DevOps
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Manual integration
- External API key
- Not required
- Operating systems
- Docker
- Runtime requirements
- Docker
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: ops-run-local
description: Manage the local Docker Compose development environment for Rails applications. Supports start…
category: devops
runtime: Docker
---
# ops-run-local output preview
## PART A: Task fit
- Use case: Manage the local Docker Compose development environment for Rails applications. Supports start, stop, restart, and status for the full stack or individual services. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Prerequisites (run before any operation) / Discovery / Operations” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Manage the local Docker Compose development environment for Rails applications. Supports start, stop, restart, and status for the full stack or individual services. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “Prerequisites (run before any operation) / Discovery / Operations” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; may access external network resources; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source mentions slash commands such as `/dev`, `/up`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Prerequisites (run before any operation) / Discovery / Operations”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: ops-run-local
description: Manage the local Docker Compose development environment for Rails applications. Supports start…
category: devops
source: tomevault-io/skills-registry
---
# ops-run-local
## When to use
- Manage the local Docker Compose development environment for Rails applications. Supports start, stop, restart, and sta…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Prerequisites (run before any operation) / Discovery / Operations” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "ops-run-local" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Prerequisites (run before any operation) / Discovery / Operations
rules -> SKILL.md triggers / order / output contract
runtime -> Docker | read files, write/modify files, run shell commands | may access external network resources
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Ops: Run Local
Manage the local Docker Compose development environment.
Argument: $ARGUMENTS — start, stop, restart, status, start-app, start-services (default: start)
Prerequisites (run before any operation)
Verify Docker is running:
docker info > /dev/null 2>&1 && echo "Docker OK" || echo "ERROR: Docker is not running — start Docker Desktop"Check port availability:
lsof -i :3000 2>/dev/null | grep LISTEN lsof -i :5432 2>/dev/null | grep LISTENVerify Ruby and Bundler are available:
ruby --version && bundle --version
Discovery
Read the project's docker-compose.yml (or compose.yaml) to identify available services. Common services include:
weborapp— the Rails applicationpostgresordb— PostgreSQL databaseworker— Solid Queue background workercss— Tailwind CSS watch process
Read Procfile.dev if it exists — it defines the local development process manager configuration (typically run via bin/dev).
Read config/database.yml to understand which databases need to exist locally.
Operations
start (full stack)
Start all Docker Compose services and the Rails application.
Start infrastructure services (PostgreSQL, etc.):
docker compose up -d postgresWait for PostgreSQL (up to 30 seconds):
for i in $(seq 1 30); do docker compose exec -T postgres pg_isready -U postgres > /dev/null 2>&1 && echo "PostgreSQL ready" && break sleep 1 doneCreate and migrate databases (if needed):
bin/rails db:prepareStart the full stack via
bin/dev(Procfile.dev) or Docker Compose:# Option A: Procfile.dev (preferred — starts web, worker, CSS watcher) bin/devRun this in the background using the Bash tool with
run_in_background: true.# Option B: Docker Compose (if all services are containerized) docker compose up -dWait for Rails (up to 60 seconds):
for i in $(seq 1 60); do curl -sf http://localhost:3000/up > /dev/null 2>&1 && echo "Rails ready" && break sleep 1 doneReport status table.
start-services (infrastructure only)
Start only infrastructure services (database, cache) without the Rails app.
docker compose up -d postgres
Wait for readiness:
for i in $(seq 1 30); do
docker compose exec -T postgres pg_isready -U postgres > /dev/null 2>&1 && echo "PostgreSQL ready" && break
sleep 1
done
start-app (Rails app only, assumes services are running)
bin/dev
Run in background. Verify:
for i in $(seq 1 60); do
curl -sf http://localhost:3000/up > /dev/null 2>&1 && echo "Rails ready" && break
sleep 1
done
stop
Stop all local services.
# Stop Rails processes (bin/dev uses foreman which spawns child processes)
lsof -ti :3000 | xargs kill -9 2>/dev/null || echo "No Rails process on :3000"
# Stop Docker Compose services
docker compose down
restart
- Run stop (above).
- Wait 2 seconds:
sleep 2 - Run start (above).
- Verify all services respond.
status
Check what is currently running and responsive.
echo "=== Port Check ==="
echo -n "Rails :3000 — "; lsof -i :3000 2>/dev/null | grep LISTEN > /dev/null && echo "LISTENING" || echo "NOT LISTENING"
echo -n "Postgres :5432 — "; lsof -i :5432 2>/dev/null | grep LISTEN > /dev/null && echo "LISTENING" || echo "NOT LISTENING"
echo ""
echo "=== Health Check ==="
echo -n "Rails /up — "; curl -sf -o /dev/null -w "HTTP %{http_code} in %{time_total}s" http://localhost:3000/up 2>/dev/null || echo "UNREACHABLE"
echo ""
echo "=== Docker Compose ==="
docker compose ps 2>/dev/null || echo "No Docker Compose services running"
echo ""
echo "=== Solid Queue Worker ==="
bin/rails runner "puts SolidQueue::Process.where('last_heartbeat_at > ?', 5.minutes.ago).count.to_s + ' active workers'" 2>/dev/null || echo "Cannot query Solid Queue (app may not be running)"
Report results as a table:
| Service | Port | Listening | Responsive |
|---|---|---|---|
| Rails (web) | 3000 | YES/NO | YES/NO |
| PostgreSQL | 5432 | YES/NO | N/A |
| Solid Queue worker | N/A | N/A | YES/NO (heartbeat) |
Source: CodySwannGT/lisa — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review