Droid Pro

Your agent for working with the Droid CLI tool — helping install, configure, and use Droid for automation, CI/CD integration, and development workflow optimization.

When to Use This Agent

Choose Droid Pro when:

• Installing and configuring the Droid CLI for your project
• Automating development workflows with Droid commands
• Integrating Droid into CI/CD pipelines (GitHub Actions, GitLab CI)
• Troubleshooting Droid CLI errors and configuration issues
• Learning Droid CLI capabilities and best usage patterns

Consider alternatives when:

• You need general CI/CD pipeline design — use a GitOps or DevOps agent
• You need code review automation — use a code reviewer agent
• You need infrastructure automation — use a Terraform or DevOps agent

Quick Start

Copy
# .claude/agents/droid-pro.yml
name: Droid Pro
model: claude-sonnet
tools:
  - Read
  - Write
  - Edit
  - Bash
  - Glob
  - Grep
description: Droid CLI specialist for installation, automation, CI/CD integration, and workflow optimization

Example invocation:

claude "Set up Droid CLI for our monorepo — configure it to run linting, testing, and type checking across all packages with proper caching"

Core Concepts

Droid CLI Workflow

Command	Purpose	Example
droid init	Initialize project configuration	Set up droid.json config
droid run	Execute configured tasks	droid run lint
droid check	Run all configured checks	Lint + test + type-check
droid fix	Auto-fix issues where possible	droid fix lint
droid ci	CI-optimized execution	Cached, parallel, fail-fast

Configuration Structure

Copy
{
  "tasks": {
    "lint": {
      "command": "eslint . --ext .ts,.tsx",
      "fix": "eslint . --ext .ts,.tsx --fix",
      "cache": true
    },
    "test": {
      "command": "vitest run",
      "watch": "vitest",
      "cache": false
    },
    "typecheck": {
      "command": "tsc --noEmit",
      "cache": true
    },
    "build": {
      "command": "vite build",
      "depends_on": ["typecheck", "lint"]
    }
  }
}

Configuration

Parameter	Description	Default
config_file	Droid configuration file path	droid.json
parallelism	Max parallel task execution	auto (CPU cores)
cache_dir	Cache directory for task results	.droid/cache
ci_mode	Optimize for CI environments	auto-detect
fail_fast	Stop on first task failure	false

Best Practices

1. Define task dependencies explicitly. When build depends on typecheck and lint, declare it in the configuration. Droid uses this dependency graph to run independent tasks in parallel and dependent tasks sequentially, optimizing total execution time.

2. Enable caching for deterministic tasks. Tasks whose output depends only on input files (linting, type-checking, building) benefit from caching. Tasks with external dependencies (integration tests, API calls) should disable caching to avoid false positives.

3. Use CI mode for pipeline execution. Droid's CI mode enables stricter output formatting, fail-fast behavior, and structured reporting. Configure it in your GitHub Actions or GitLab CI workflow to get machine-readable output and proper exit codes.

4. Separate fix commands from check commands. Configure both droid check (validate, report errors) and droid fix (auto-fix where possible). This allows CI to check without modifying code, while developers can fix issues locally with a single command.

5. Cache the Droid cache between CI runs. Use your CI platform's cache mechanism (actions/cache for GitHub) to persist Droid's cache directory between pipeline runs. This significantly reduces CI execution time for unchanged code.

Common Issues

Droid CLI not found after installation. The CLI binary may not be in your PATH. Check the installation location, add it to your shell profile (~/.bashrc, ~/.zshrc), and restart your terminal. For CI environments, ensure the install step runs before any Droid commands.

Cached results produce false negatives. When external dependencies change (a new ESLint rule, updated TypeScript config), cached results may not reflect the new rules. Clear the cache (droid cache clean) after modifying tool configurations.

Tasks run sequentially despite being independent. Check that your task configuration doesn't include unnecessary depends_on relationships. Tasks without dependencies automatically run in parallel. Verify with droid graph to visualize the dependency tree.