ovo-cli-dev

Creates and wires new ovo CLI commands with dispatcher integration and build.zig registration.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/donaldfilimon/ovo --skill ovo-cli-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ovo-cli-dev
Source: https://github.com/donaldfilimon/ovo/tree/main/.claude/plugins/ovo/skills/ovo-cli-dev
Command: npx skills add https://github.com/donaldfilimon/ovo --skill ovo-cli-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enables developers to create and wire new OVO CLI commands, ensuring consistent structure, dispatcher wiring, and build.zon round-trip compatibility.

Core Features & Use Cases

  • Provides a canonical command template, dispatcher wiring guidance, and build.zon round-trip conventions.
  • Documents required module wiring, command file naming, and usage/help conventions for uniform UX.
  • Use Case: A developer adds a new ovo command, wires it into the dispatcher, and registers it in build.zig so it is accessible via ovo.

Quick Start

Create the new command following the template with a file at src/cli/<name>_cmd.zig, wire it into the dispatcher in src/cli/commands.zig, register in build.zig, and build to verify.

Frequently Asked Questions about ovo-cli-dev

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

FAQPage Schema
How do I add a new command to a Zig CLI dispatcher?

To add a new command to a Zig CLI dispatcher, create a command file at src/cli/<name>_cmd.zig, wire it into the dispatcher in src/cli/commands.zig, and register it in build.zig to ensure it is accessible.

What is the correct file structure for creating OVO CLI commands?

The correct file structure for creating OVO CLI commands requires a Command Zig file following the <name>_cmd.zig pattern in src/cli, standardized output hooks, and help text integrated with the dispatcher.

How do I register a new command in build.zig without breaking round-trips?

To register a new command in build.zig without breaking round-trips, you must apply build.zon round-trip conventions during command registration to maintain consistent build compatibility.

Does this CLI command development process require updating the dispatcher manually?

Yes, the CLI command development process requires updating the dispatcher manually in src/cli/commands.zig to wire the new command module and ensure uniform user experience.

What's the best way to ensure consistent help text and output hooks across CLI commands?

The best way to ensure consistent help text and output hooks across CLI commands is to apply a canonical command template that documents required module wiring and usage conventions.

Why does my new Zig CLI command fail to build after dispatcher wiring?

If your new Zig CLI command fails to build after dispatcher wiring, it likely indicates an incorrect build.zig registration or a broken build.zon round-trip compatibility that needs verification.