services up

DevOps Community

Skill notes

Start services. If $ARGUMENTS is provided, start only those services; otherwise start all.

!docker compose up -d ${ARGUMENTS:-todo-backend todo-frontend jira-mock} 2>&1

Then wait for the backend to be healthy:

!for i in $(seq 1 15); do curl -sf http://localhost:8000/health && echo "backend ready" && break || sleep 2; done 2>&1

Report: - Which containers are now running (docker compose ps) - Health check result for the backend - If any container failed to start, show its logs

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Docker
Runtime requirements
Docker
Detected file/system behavior
  • Read-only
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

Start services. If `$ARGUMENTS` is provided, start only those services; otherwise start all.

!`docker compose up -d ${ARGUMENTS:-todo-backend todo-frontend jira-mock} 2>&1`

Then wait for the backend to be healthy:

!`for i in $(seq 1 15); do curl -sf http://localhost:8000/health && echo "backend ready" && break || sleep 2; done 2>&1`

Report:
- Which containers are now running (`docker compose ps`)
- Health check result for the backend
- If any container failed to start, show its logs

---
> Source: [brianbartilet/testing-lifecycle-with-agents-demo](https://github.com/brianbartilet/testing-lifecycle-with-agents-demo) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.