devhub

majiayu000's avatarfrom majiayu000

Generate devhub.toml configuration files and manage multi-project development environments. Use when setting up projects, creating service configs, starting/stopping services, checking status, or managing development workflows. Triggers on mentions of devhub, project setup, service management, or development environment configuration.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026

When & Why to Use This Skill

DevHub is a comprehensive development environment manager designed to streamline multi-project workflows and local service orchestration. It automates the creation of configuration files, provides intelligent project auto-detection, and offers a centralized interface to start, stop, and monitor various services, significantly enhancing developer productivity and environment consistency.

Use Cases

  • Automated Project Setup: Quickly initialize new development environments by auto-detecting project types (such as Node.js, Python, Rust, or Docker) and generating optimized devhub.toml configurations.
  • Microservices Orchestration: Manage complex architectures by starting, stopping, or restarting multiple local services simultaneously with simple commands, reducing manual terminal overhead.
  • Centralized Service Monitoring: Monitor the real-time status and logs of all registered projects from a single dashboard to identify and debug issues across different services efficiently.
  • Workflow Standardization: Use the project registry and favorite features to maintain a consistent development workspace across multiple repositories and monorepos.
  • Conflict Resolution: Detect and prevent port conflicts between different local services using built-in port checking tools.
namedevhub
descriptionGenerate devhub.toml configuration files and manage multi-project development environments. Use when setting up projects, creating service configs, starting/stopping services, checking status, or managing development workflows. Triggers on mentions of devhub, project setup, service management, or development environment configuration.

DevHub Skill

DevHub is a multi-project development environment manager that lets you start, stop, and monitor all your local development services from one place.

When to Use This Skill

Use DevHub when the user wants to:

  • Set up a new project for local development
  • Generate a devhub.toml configuration file
  • Start, stop, or restart development services
  • Check the status of running services
  • Manage multiple projects or services
  • View logs from services
  • Manage favorite projects

Primary Workflow: Setting Up a New Project

Step 1: Preview Discovery (Always Do This First)

devhub discover --dry-run

This shows what DevHub would detect without writing any files. Review the output with the user before proceeding.

Step 2: Generate Configuration

If the preview looks correct:

devhub discover

This creates devhub.toml in the project root.

Step 3: Register the Project

devhub register

This adds the project to DevHub's registry so it can be managed globally.

Step 4: Start Services

devhub start

Or start a specific service:

devhub start -s api

Key Commands Quick Reference

Command Purpose
devhub discover --dry-run Preview auto-detection
devhub discover Generate devhub.toml
devhub register Add project to registry
devhub start [project] Start all services
devhub stop [project] Stop all services
devhub status Show all project statuses
devhub logs <project> -f Follow service logs
devhub list List all registered projects

Supported Project Types

DevHub auto-detects these project types:

Type Detection File Default Command
Rust Cargo.toml cargo run
Node.js package.json npm run dev
Python (UV) pyproject.toml uv run python
Python (pip) requirements.txt python
Go go.mod go run .
Flutter pubspec.yaml flutter run
Docker docker-compose.yml docker compose up

Monorepo Support

When no root project marker is found, DevHub scans subdirectories and creates a multi-service configuration automatically.

Additional Reference

For detailed information, see:

Best Practices

  1. Always preview first: Run devhub discover --dry-run before generating config
  2. Review generated config: Check the devhub.toml and adjust ports/commands if needed
  3. Use favorites: Mark frequently-used projects with devhub fav add <project>
  4. Check for conflicts: Run devhub ports --check to detect port conflicts
  5. Follow logs: Use devhub logs <project> -f to monitor service output