From data-engineering
Manage local Airflow environment with Astro CLI. Use when the user wants to start, stop, or restart Airflow, view logs, troubleshoot containers, or fix environment issues. For project setup, see setting-up-astro-project.
How this skill is triggered — by the user, by Claude, or both
Slash command
/data-engineering:managing-astro-local-envThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill helps you manage your local Airflow environment using the Astro CLI.
This skill helps you manage your local Airflow environment using the Astro CLI.
To set up a new project, see the setting-up-astro-project skill. When Airflow is running, use MCP tools from authoring-dags and testing-dags skills.
# Start local Airflow (webserver at http://localhost:8080)
astro dev start
# Stop containers (preserves data)
astro dev stop
# Kill and remove volumes (clean slate)
astro dev kill
# Restart all containers
astro dev restart
# Restart specific component
astro dev restart --scheduler
astro dev restart --webserver
Default credentials: admin / admin
Restart after modifying: requirements.txt, packages.txt, Dockerfile
astro dev ps
# All logs
astro dev logs
# Specific component
astro dev logs --scheduler
astro dev logs --webserver
# Follow in real-time
astro dev logs -f
# Bash into scheduler container
astro dev bash
# Run Airflow CLI commands
astro dev run airflow info
astro dev run airflow dags list
| Issue | Solution |
|---|---|
| Port 8080 in use | Stop other containers or edit .astro/config.yaml |
| Container won't start | astro dev kill then astro dev start |
| Package install failed | Check requirements.txt syntax |
| DAG not appearing | Run astro dev parse to check for import errors |
| Out of disk space | docker system prune |
When things are broken:
astro dev kill
astro dev start
astro dev upgrade-test
Edit Dockerfile:
FROM quay.io/astronomer/astro-runtime:13.0.0
Restart:
astro dev kill && astro dev start
npx claudepluginhub pjunn/airflow-agentsGuides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Guides reception of code review feedback: verify before implementing, avoid performative agreement, push back with technical reasoning when needed.
Manages knowledge base ingestion, sync, and retrieval across local files, MCP memory, vector stores, and Git repos. Use for saving, organizing, deduplicating, or searching knowledge.