dotagent:new-command

Add new Clap subcommands to the dotagent CLI with enum variants and routing.

3|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/avelino/dotagent --skill dotagent-new-command
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotagent:new-command
Source: https://github.com/avelino/dotagent/tree/main/.claude/skills/new-command
Command: npx skills add https://github.com/avelino/dotagent --skill dotagent-new-command

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the process of expanding the dotagent CLI by providing a structured approach to add new subcommands. It ensures consistent wiring from the CLI surface (enum variants) to command handlers and documentation, reducing manual drift and errors.

Core Features & Use Cases

  • Adds a new Clap subcommand by updating the Command enum, the match logic, and the implementation module.
  • Ensures consistent help text, validation, and safe defaults for extensibility.
  • Applies to scenarios like exposing new agent actions (tick, status, inspect) or domain-specific commands while preserving wiring and testability.

Quick Start

Add a new subcommand named my-command and wire it through main.rs and commands/ to expose it in the CLI.

Frequently Asked Questions about dotagent:new-command

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new subcommand to a Rust CLI using clap?

To add a new subcommand to a Rust CLI using clap, you update the Command enum, modify the match routing logic, and implement the new module to ensure consistent wiring and help text.

What is the best way to extend a Rust orchestrator with domain-specific actions?

Extending a Rust orchestrator with domain-specific actions involves adding consistent enum variants and routing for new commands like install, run, or inspect, while preserving testability and safe defaults.

How does adding a CLI subcommand affect existing Rust command modules?

Adding a CLI subcommand requires updating main.rs and command modules to wire the new action, enforcing validation, formatting, and test updates to prevent manual drift and routing errors.

Do I need to update tests when wiring a new clap subcommand in Rust?

Yes, updating tests is required when wiring a new clap subcommand in Rust. The workflow enforces test updates alongside changes to main.rs and command modules to maintain CLI testability.

Can I expose agent actions like tick or status as CLI commands in Rust?

Yes, you can expose agent actions like tick, status, or inspect as CLI commands in Rust by applying structured subcommand extension to map these domain-specific actions through the command enum.

Why does my Rust CLI subcommand routing drift from the implementation module?

Routing drifts from the implementation module when CLI surface updates lack a structured approach, which this workflow prevents by enforcing consistent wiring from the command enum to handlers and help text.