cli-maintenance

Synchronize CLI command implementations with documentation, slash commands, and MCP registries.

13|1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Generous-Corp/pulp --skill cli-maintenance-generous-corp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-maintenance
Source: https://github.com/Generous-Corp/pulp/tree/main/.agents/skills/cli-maintenance
Command: npx skills add https://github.com/Generous-Corp/pulp --skill cli-maintenance-generous-corp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill manages the complex synchronization required when adding, modifying, or removing CLI commands, ensuring that source code, slash commands, documentation, and agent-accessible tools remain perfectly aligned.

Core Features & Use Cases

  • Consistency Enforcement: Validates that new CLI commands are correctly registered in C++ tables, Rust source, and YAML manifests.
  • Workflow Automation: Provides a decision tree for determining when to create slash commands or MCP tools, preventing architectural drift.
  • Use Case: When adding a new subcommand, use this skill to verify that your implementation, documentation, and parity checks satisfy all repository requirements before pushing your changes.

Quick Start

Run the cli-maintenance skill to perform a full consistency check on your current CLI command modifications.

Frequently Asked Questions about cli-maintenance

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

FAQPage Schema
How do I keep CLI commands synchronized with documentation and MCP tool registries?

CLI command synchronization aligns source code, slash commands, documentation, and agent-accessible tools. Automated validation scripts verify registrations across C++ tables, Rust source, and YAML manifests to maintain cross-platform parity.

What is the best way to enforce consistency when adding new CLI subcommands?

Enforcing CLI consistency requires validating new subcommands against repository-wide build governance. Automated checks confirm correct registration in C++ tables, Rust source, and YAML manifests before pushing changes.

How do I know whether to create a slash command or an MCP tool for a new CLI feature?

A decision tree determines whether to create slash commands or MCP tools, preventing architectural drift. It evaluates the feature requirements against repository tool-registry standards to guide the correct implementation path.

Does this CLI maintenance process work with both C++ and Rust source trees?

Yes, CLI maintenance supports both C++ and Rust source trees. It facilitates the maintenance of cross-platform command tables and performs parity checks to ensure command implementations match across both environments.

What limitations exist when validating CLI commands against build governance standards?

Validation is limited to repository-wide build governance and tool-registry standards compliance. It verifies parity across C++ and Rust source trees but does not extend beyond the defined automated validation script scope.