Have Autohand Code use CLI tool skill patterns to add commands, flags, validation, help output, config loading, and tests.
Create a command-line workflow with flags and help text
Developer tooling Build and change Implementation Code
autohand -p "Build this CLI command with flags, help text, validation, and tests"
A working CLI command with predictable flags, useful errors, docs, and validation tests.
Build a CLI tool with Autohand Code is a developer-tooling workflow that adds a command-line tool or command with flags, validation, help output, config handling, and tests. ### At a glance | Question | Answer | | --- | --- | | Best for | internal scripts that need stable arguments, user-facing developer tools, and repeated terminal workflows | | Primary inputs | Command name, arguments, and expected outputs; Existing CLI framework or package scripts; Error cases, config needs, and test command | | Autohand Code returns | A working CLI command with predictable flags, useful errors, docs, and validation tests. | | Avoid when | a one-off shell snippet is enough and no one will reuse the command | ### How Autohand Code handles this workflow 1. Finds the existing CLI framework, entry point, and command style. 2. Adds flags, validation, help text, and useful exit behavior. 3. Handles config and environment values through the repo pattern. 4. Adds tests or smoke checks and documents examples. ### Best inputs - Command name, arguments, and expected outputs - Existing CLI framework or package scripts - Error cases, config needs, and test command ### Strong prompt autohand -p "Build this CLI command with flags, help text, validation, and tests" ### Autohand Code CLI options - Use `/skills use cli-tool-development` for command structure and help-text patterns. - Run `autohand -p "Build this CLI command with flags, help text, validation, and tests"` with example invocations. - Use `AUTOHAND_NON_INTERACTIVE=1` when the new command is part of a scripted workflow. ### Review before accepting Check help output, invalid input behavior, example commands, and tests for the new command path. ### Source and validation signals Autohand AI maintains this workflow as first-party product guidance for Autohand Code. Use the [Autohand CLI Playbook](https://github.com/autohandai/code-cli/blob/main/docs/AUTOHAND_PLAYBOOK.md), [CLI reference](/docs/working-with-autohand-code/cli-reference.html), and [configuration reference](https://github.com/autohandai/code-cli/blob/main/docs/config-reference.md) when choosing between interactive mode, command mode, auto-mode, feature-enabled /goal, /settings, skills, MCP, and permission settings. The related resources below link to product docs and tutorials for the workflow, and the final answer should name repository-specific files, commands, outputs, or docs that a reviewer can verify. ### Frequently asked questions ### What is Build a CLI tool with Autohand Code? Build a CLI tool with Autohand Code is a developer-tooling workflow that adds a command-line tool or command with flags, validation, help output, config handling, and tests. ### When should a team use Build a CLI tool? Use it when a repeated developer task deserves a reliable CLI surface. ### What evidence should reviewers check for Build a CLI tool? Check help output, invalid input behavior, example commands, and tests for the new command path.
Skill Skilled: CLI Tool Development Use CLI structure, flags, and testing patterns. https://skilled.autohand.ai/skill/cli-tool-development Tutorial Build a CLI Tool Create terminal workflows with Autohand Code. /docs/tutorials/build-cli-tool.html Reference CLI Reference Review Autohand Code command-mode options. /docs/working-with-autohand-code/cli-reference.html