dev-cli-development

Create a new CLI command by defining a function with Click decorators in src/aidb_cli/, use @click.command() to register it, add options with @click.option(), and wire it into your command group. Encapsulate business logic in a BaseService-derived service class for reusability and testability.

Use the @handle_exceptions decorator on your command functions to implement unified error handling across all CLI commands. This ensures consistent error reporting, proper exit codes, and aligns with AIDB's error management patterns.

Use Click's context injection via @click.pass_context and ctx.obj to store and retrieve shared data between commands. This pattern integrates service instances and configuration state without coupling commands directly.

Yes, define custom Click parameter types to validate and transform user input before it reaches your command. AIDB's dev-cli supports dynamic parameter types for specialized input handling aligned with framework best practices.

Wire Docker and test adapter systems through BaseService patterns and decorators in your command implementation. Use the CommandExecutor with hash-based cache invalidation and docker-compose generation workflows to automate complex development tasks.

Separating CLI command structure from business logic via BaseService classes creates reusable, testable, and maintainable code. Services can be called independently from other tools and remain decoupled from Click framework specifics.