cli

Document CLI development practices for the LobeHub project.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/andershi666/lobehub-hr-demo --skill cli-andershi666
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli
Source: https://github.com/andershi666/lobehub-hr-demo/tree/main/lobehub/.agents/skills/cli
Command: npx skills add https://github.com/andershi666/lobehub-hr-demo --skill cli-andershi666

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Document CLI development practices for the LobeHub project, including command patterns, architecture, and contributor workflows.

Core Features & Use Cases

  • Patterns for adding new commands, implementing subcommands, and integrating with the internal API.
  • Guidelines for running in development mode, testing locally, and validating behavior against a local server.

Quick Start

From the project root, start development mode and run a sample command to verify the CLI workflow.

Frequently Asked Questions about cli

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

FAQPage Schema
What are the conventions for command development in the LobeHub CLI?

To develop LobeHub CLI commands, you follow specific patterns for adding new commands, implementing subcommands, and integrating with the internal API. It enforces frontmatter requirements and references usage to ensure consistent discovery and maintainability.

How do I run the LobeHub CLI in development mode against a local server?

Running in development mode requires starting the local server from the project root to test locally. You then execute a sample command to validate behavior against the running server before extending the CLI.

How do I add new subcommands and integrate them with the internal API?

Adding new subcommands involves following established architecture patterns to integrate with the internal API. You implement the command logic and validate its behavior locally during development mode to ensure correct API integration.

Do I need to follow specific frontmatter and references conventions for CLI contributions?

Yes, CLI contributions strictly enforce frontmatter requirements and references usage. Adhering to these development conventions ensures consistent command discovery and long-term maintainability across the LobeHub project.

What is the architecture for extending the LobeHub CLI as a contributor?

The CLI architecture provides structured contributor workflows for extending functionality. It covers command patterns, local testing procedures, and integration points with the internal API to guide developers through the extension process.