setup-environment
Set up or verify the local development environment. Use when starting work in a fresh clone or new machine, when commands fail with missing dependencies or broken imports, or before running `make check`/`make test` for the first time in a session.
Best use case
setup-environment is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Set up or verify the local development environment. Use when starting work in a fresh clone or new machine, when commands fail with missing dependencies or broken imports, or before running `make check`/`make test` for the first time in a session.
Teams using setup-environment should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/setup-environment/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How setup-environment Compares
| Feature / Agent | setup-environment | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Set up or verify the local development environment. Use when starting work in a fresh clone or new machine, when commands fail with missing dependencies or broken imports, or before running `make check`/`make test` for the first time in a session.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Setup Environment Set up or verify the local development environment. ## Steps ### 1. Run setup ```bash make setup ``` This installs all dependencies, pre-commit hooks, and verifies that the linter, type-checker, CLI entrypoint, and test collection all work. ### 2. If setup fails, diagnose - **`python3 --version` reports < 3.11** — ask the user to install a supported Python version. - **`uv` not found** — install it: `curl -LsSf https://astral.sh/uv/install.sh | sh` - **`uv sync --dev` fails** — check for conflicting lockfiles or network issues and report the error. - **`databao --help` fails** — broken import; diagnose before proceeding with any other work. - **Lint / type-check / test collection fails** — likely a code issue, not an environment issue. Investigate the specific error. ## What this skill does NOT do - Run the full test suite — use `make test` for that. - Configure cloud credentials or Docker for E2E tests. - Modify `pyproject.toml` or add new dependencies.