cli

Standardize LobeHub CLI development workflows for commands, tests, and documentation.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Nick777-Pixel/mychat7 --skill cli-nick777-pixel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli
Source: https://github.com/Nick777-Pixel/mychat7/tree/main/.agents/skills/cli
Command: npx skills add https://github.com/Nick777-Pixel/mychat7 --skill cli-nick777-pixel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The CLI development guide consolidates standards, architecture, and workflows to accelerate building, testing, and maintaining the LobeHub command-line interface.

Core Features & Use Cases

  • Architecture overview: entry points, command groups, and runtime structure for apps/cli.
  • Contributor onboarding: quick references for adding subcommands, tests, and docs.
  • Quality patterns: output formatting, authentication hooks, and error handling conventions.

Quick Start

Install dependencies and begin implementing a new command using the existing CLI project structure.

Frequently Asked Questions about cli

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

FAQPage Schema
How do I add a new command to a Node.js CLI?

To add a new command to a Node.js CLI, you should follow the project's architecture overview to locate entry points and command groups, then implement the subcommand using established runtime structures.

What is the standard workflow for TypeScript CLI development?

The standard workflow for TypeScript CLI development involves automating and standardizing tasks across the project, including implementing commands, writing tests, and maintaining documentation to ensure consistent architecture.

How do I handle errors and format output in a command-line application?

Handling errors and formatting output in a command-line application requires following quality patterns that define output formatting, authentication hooks, and error handling conventions for consistent CLI behavior.

Does this CLI development guide support contributor onboarding?

Yes, this CLI development guide supports contributor onboarding by providing quick references for adding subcommands, writing tests, and generating documentation within the existing project structure.

Why do my CLI tests keep failing after adding new subcommands?

CLI tests may fail after adding new subcommands if the new code does not adhere to the project's quality patterns for error handling or if the command structure does not match the expected runtime architecture.

Can I use this guide to debug the architecture of an existing command-line tool?

Yes, you can use this guide to debug the architecture of an existing command-line tool by referencing its overview of entry points, command groups, and runtime structure to identify and resolve structural issues.