- name
- local-setup-and-run
- description
- Explain and validate local setup paths for this repository with Docker and without Docker. Use when developers need exact prerequisites, startup commands, health checks, and troubleshooting.
# Local Setup And Run Skill
## Mission
Provide accurate local setup/run instructions based on this repository's actual build and run scripts.
## Scope
In scope:
- local run documentation and runbook changes
- command mapping from `README.md`, `justfile`, `just/`, and compose files
- prerequisites and troubleshooting guidance
Out of scope:
- application feature implementation changes
- provider integration behavior changes unrelated to setup
## Source-of-truth files
- `README.md`
- `justfile` and `just/*.just`
- `docker-compose.yml`
- `docker-compose.knowledge.yml`
## Required output
1. Docker path (recommended) with commands.
2. Docker knowledge mode path.
3. Non-Docker path with dependencies and `run-*` commands.
4. Health-check URLs and expected ports.
5. Troubleshooting section.
## Lifecycle integration
- `development-lifecycle` owns tier selection and the repository-level change contract.
- Use `change-analysis` when ownership, consumers, or blast radius is not already proven.
- This skill owns its domain evidence and boundaries; `developing-change` owns implementation discipline.
- Use `debugging` for unexplained failures and `writing-documentation` for documentation changes.
- Use `reviewing-change` for independent review and `responding-to-review` for its findings.
- Use `preparing-delivery` only when the user explicitly requests a delivery action.
## Governed lifecycle
- Classify work as Fast, Standard, or Governed using `DEVELOPMENT_PROCESS.md`; use the full gated lifecycle only for Governed work.
- This skill operates only in its assigned phase and path ownership; it may not approve its own plan or code review.
- Governed repository edits start only from a coordinator-attested approved plan; Fast and Standard work follows its lighter documented lifecycle.
- Return documentation and verification evidence to the coordinator, then route the complete verified diff to the read-only `code-reviewer`.
## Validation commands
- `just --list`
- `just up-all`
- `just up-all-with-knowledge`
- `just deps`
- `docker compose ps`
## References
- `references/checklist.md`
- `examples/sample.md`
Ver en GitHub