create-cli

Name: create-cli
Availability: InStock
Author: Corca

Define and bootstrap repo-owned CLI surfaces with entrypoints and governance.

9|3|Updated Apr 9, 2026

Search Tags:#cli #developer-tools #bootstrap #quality-gates #dry-run #surface-design #command-surface

Ready to run

npx skills add https://github.com/corca-ai/charness --skill create-cli-corca-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-cli
Source: https://github.com/corca-ai/charness/tree/main/plugins/charness/skills/create-cli
Command: npx skills add https://github.com/corca-ai/charness --skill create-cli-corca-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Create and evolve a repo-owned CLI surface with a defined command namespace, install/update contracts, deterministic outputs, and built-in governance for dry-run and doctor workflows.

Core Features & Use Cases

Define a stable command surface and lifecycle verbs (init, doctor, update, reset, uninstall) for a repo-owned CLI.
Specify deterministic bootstrap pathways, structured outputs, and governance gates to ensure reliability.
Use cases include adding a new CLI tool to a project, upgrading an existing CLI, or standardizing command surfaces across multiple tools.

Quick Start

Describe a new CLI surface for a project by outlining its entrypoints and governance rules, then implement a bootstrap plan.

Frequently Asked Questions about create-cli

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

FAQPage Schema

How do I bootstrap a reliable CLI surface for a software project?▼

To bootstrap a reliable CLI surface, define explicit entrypoints and an install/update contract, then establish structured outputs and diagnostic hooks for dry-run and doctor workflows to ensure operator-friendly reliability.

What are lifecycle verbs for a repo-owned CLI command surface?▼

Lifecycle verbs for a repo-owned CLI command surface include init, doctor, update, reset, and uninstall, which define a stable command namespace and deterministic bootstrap pathways for project operators.

How do I add a dry-run diagnostic hook to a command line interface?▼

You add a dry-run diagnostic hook by specifying deterministic bootstrap pathways and governance gates within your CLI surface, ensuring structured outputs validate command execution without applying state changes.

Can I standardize command surfaces across multiple CLI tools?▼

Yes, you can standardize command surfaces across multiple CLI tools by defining a shared command namespace, install/update contracts, and structured outputs, ensuring consistent governance checks across all project tools.

Does my CLI need quality gates for release readiness?▼

Your CLI needs quality gates for release readiness to enforce governance checks, deterministic outputs, and reliable doctor workflows, ensuring the command surface remains stable and operator-friendly during updates.