li3p/env-check

Environment Check

Assess whether the current repository is ready for local development.

Workflow

1. Identify project requirements from files such as:
   • .node-version, .nvmrc, .python-version, .tool-versions
   • package.json, pyproject.toml, requirements.txt, Gemfile
   • .env.example, .env.sample, docker-compose.yml
   • migration or ORM config files
2. Compare required runtimes with installed runtimes.
3. Check whether dependencies appear installed and current.
4. Compare example environment variables with local environment files. Never print secret values.
5. Check whether required local services are running when the repo declares them, such as Postgres, Redis, queues, or Docker Compose services.
6. Check whether migrations or generated artifacts appear out of date.
7. Check whether expected git hooks or pre-commit tooling are installed.

Output

Return a checklist grouped by category:

• OK: requirement is satisfied.
• MISSING: required item is absent.
• MISMATCH: installed or local value differs from the repo requirement.
• UNKNOWN: could not verify safely.

For every MISSING or MISMATCH item, include the exact command or file change needed to fix it. Do not modify files unless the user explicitly asks.