// Set up the development environment for the project. Use when starting work on the project, when dependencies are out of sync, or to fix environment setup failures.
Manage Architecture Decision Records (ADRs) using adr-tools. Use this to initialize, create, list, and link ADRs to document architectural evolution.
Scaffold and standardize new dbt-helpers plugins (Warehouse, Tool, or Schema). Use when starting a new plugin implementation or updating plugin discovery configuration.
Comprehensive workflow for creating, implementing, and validating Agent Skills. Use when asked to "create a new skill", "author a skill", "add a capability", or when standardizing project-specific workflows. Support for platform detection (Cursor, Claude Code, Gemini CLI, Codex) and template selection.
Implement and run End-to-End tests using golden output comparison. Use when verifying CLI behavior, plan generation, or full project execution.
Set up and run integration tests using Testcontainers. Use when testing warehouse adapters against real database engines or verifying filesystem-dependent operations.
Implement and use Nullable Infrastructure adapters for mock-free testing. Use when writing unit tests for core logic, implementing infrastructure adapters, or setting up test fixtures.
| name | setup-dev-env |
| description | Set up the development environment for the project. Use when starting work on the project, when dependencies are out of sync, or to fix environment setup failures. |
This skill automates the process of setting up the development environment to ensure all tools and dependencies are correctly installed and configured.
.python-versiontrunk installation (including /opt/homebrew/bin/trunk)uv installation (including /opt/homebrew/bin/uv)trunk-io and uv via Homebrew if missingPATHmake setuptrunk install to fetch managed linters and formattersRead the .python-version file in the workspace root. Ensure the current Python environment matches this version. If there's a mismatch, inform the user to switch Python versions (e.g., using pyenv or asdf).
Check if trunk and uv are installed and available in the current PATH.
On macOS, prioritize Homebrew installation to avoid common pathing and permission issues.
Check common locations:
/opt/homebrew/bin/trunk/opt/homebrew/bin/uvIf these tools are missing, install them via Homebrew:
brew install --cask trunk-io
brew install uv
CRITICAL: If the binaries exist in /opt/homebrew/bin/ but are not in the current shell's PATH, advise the user to add it:
export PATH="/opt/homebrew/bin:$PATH"
Run the following command at the workspace root to install all project dependencies.
make setup
This command runs dev/setup.sh, which performs informative checks for uv and trunk, creates a virtual environment, and syncs dependencies.
Trunk manages linters and formatters hermetically. Run the following command to ensure all required tools are downloaded and ready.
trunk install
trunk and uv are installed..python-version.To ensure the environment is fully operational:
verifier subagent (../../agents/verifier.md). This confirms that the freshly installed dependencies allow for a successful build, pass lint checks, and satisfy all unit tests.verifier fails, follow its reporting to resolve environment-specific issues.