Skip to Content
ReferenceCLI Commands Reference

CLI Commands Reference

Complete reference for all Dotpack CLI commands with options, examples, and usage patterns.

Core Commands

dotpack init

Purpose: Initialize Dotpack in the current project
Creates: .dotpack/ configuration and adapter files

dotpack init

Options:

  • --yes, -y — Skip prompts, auto-select all adapters, and overwrite existing configuration
  • --adapter <name>, -a — Select specific adapter (legacy mode)

Examples:

# Interactive selection (recommended) dotpack init # Auto-select all adapters and skip prompts dotpack init --yes # Single adapter (legacy) dotpack init --adapter cursor

Interactive Prompt:

? Which adapters would you like to enable? ❯◉ Gemini CLI - AI assistant for Google Gemini CLI ◉ Cursor Rules - AI rules for Cursor editor ◉ Claude Code - Anthropic's Claude Code assistant

Output:

✓ Created .dotpack/ configuration ✓ Generated .gemini/ adapter files ✓ Generated .cursor/ adapter files ✓ Generated .claude/ adapter files 🎉 Dotpack initialized successfully!

dotpack customize

Purpose: Initialize Dotpack with a custom selection of agents, commands, and skills.

dotpack customize

Options:

  • --adapter <name>, -a — Target adapter (default: “gemini”)
  • --pack <name>, -p — Pack template (default: “engineer”)

Examples:

# Interactive customization dotpack customize # Customize with specific adapter and pack dotpack customize --adapter cursor --pack engineer

dotpack build

Purpose: Regenerate adapter output files from .dotpack/ source
When to use: After modifying configurations or adding components

dotpack build [adapter]

Arguments:

  • [adapter] — Optional: Build specific adapter only (e.g., gemini, cursor)

Examples:

# Rebuild all enabled adapters dotpack build # Rebuild specific adapter dotpack build gemini

Output:

🔄 Regenerating adapter output... ✓ Rebuilt 3 adapter(s)

dotpack add

Purpose: Add individual components (commands, agents, skills)

dotpack add <type> <name>

Arguments:

  • <type> — Type of component: agent, command, or skill
  • <name> — Name of the item to add

Examples:

# Add a command dotpack add command deploy # Add an agent dotpack add agent qa # Add a skill dotpack add skill react

Output:

✓ Added command: deploy

dotpack list

Purpose: List installed components or available packs

dotpack list [type]

Arguments:

  • [type] — Optional filter: agents, commands, skills, or packs

Examples:

# List all installed components dotpack list # List specific types dotpack list commands dotpack list agents # List available packs (global) dotpack list packs

License Management

dotpack activate

Purpose: Activate your Dotpack license
Required: License key from purchase

dotpack activate <key>

Options:

  • --local — Use local development API
  • --dev — Development mode (bypass validation)

Examples:

# Standard activation dotpack activate DP-ABC123-DEF456...

Output:

✅ License key activated successfully! Your CLI is now ready to use.

dotpack status

Purpose: Check license status and pack availability

dotpack status

Output:

License Information: Key: DP-ABC1... Status: ✅ Valid Expires: 12/31/2025 Activations: 1/3 Available Packs: engineer

dotpack license

Purpose: Manage your Dotpack license (currently an alias for checking status)

dotpack license

dotpack deactivate

Purpose: Deactivate license on current machine

dotpack deactivate

Use case: Moving license to another machine

Output:

✓ License deactivated

Global Options

Available for all commands:

OptionDescription
--help, -hShow help information
--version, -VShow version number

Exit Codes

CodeMeaning
0Success
1General error / Failure
Last updated on