CLI Command Wiring

Wire new CLI commands into cli-entry.ts with run functions and help text.

3.1k|475|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/bradygaster/squad --skill cli-command-wiring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: CLI Command Wiring
Source: https://github.com/bradygaster/squad/tree/main/.squad/skills/cli-wiring
Command: npx skills add https://github.com/bradygaster/squad --skill cli-command-wiring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the common issue where new CLI commands are implemented but not properly integrated into the command-line interface's routing and help system, leading to uncallable commands.

Core Features & Use Cases

  • Command Implementation: Guides the creation of new command files with run<Name> functions.
  • Routing Integration: Details how to add new commands to the CLI's main entry point (cli-entry.ts).
  • Help Text Generation: Explains how to update the CLI's help messages for discoverability.
  • Use Case: When a developer adds a new feature like squad publish, this Skill ensures it's not only functional but also accessible via squad publish and documented in the help output.

Quick Start

Add a new command file for 'deploy' in packages/squad-cli/src/cli/commands/deploy.ts and wire it in cli-entry.ts.

Frequently Asked Questions about CLI Command Wiring

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

FAQPage Schema
How do I wire a new CLI command into the main entry point?

To wire a new CLI command, you add a command file with a `run<Name>` function and import it into the main `cli-entry.ts` file. This ensures the command logic is properly routed and accessible via the command-line interface.

Why does my newly implemented CLI command show as uncallable?

Your CLI command is uncallable because it has not been properly integrated into the command-line interface's routing system. You must update the main entry point and help system to make the new command accessible to users.

How do I update help text for a new command-line tool feature?

Updating help text for a command-line tool requires modifying the CLI's help messages during the command integration process. This ensures the new command is discoverable and properly documented in the help output for users.

Do I need specific file structures for lazy loading CLI commands?

Yes, you need specific file structures and import patterns to enable lazy loading of CLI commands. Adhering to these structural requirements ensures newly implemented commands are correctly routed and documented within the interface.

What is the best way to document TypeScript CLI commands?

The best way to document TypeScript CLI commands is to wire them into the help system during implementation. This involves updating the CLI's help messages in the entry point to ensure features are discoverable and accessible.