rules-cmd

Name: rules-cmd
Availability: InStock
Author: flext-sh

Validate command entrypoints and package wiring in the cmd/ directory.

Updated May 20, 2025

Search Tags:#code quality #developer tools #validation #cli #command line #entrypoint

Ready to run

npx skills add https://github.com/flext-sh/flext --skill rules-cmd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rules-cmd
Source: https://github.com/flext-sh/flext/tree/main/.claude/skills/rules-cmd
Command: npx skills add https://github.com/flext-sh/flext --skill rules-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill ensures that command-line entrypoints within the cmd/ directory are well-structured, consistently named, and properly documented, preventing ambiguity and improving the developer experience.

Core Features & Use Cases

Command Structure Validation: Enforces rules for thin command entrypoints, focusing on parsing and dispatch.
Naming Consistency: Ensures command paths and names align with their directory structures.
Documentation Anchoring: Verifies that documentation and references point to actual command files.
Use Case: When adding a new command-line tool or modifying an existing one, this Skill helps maintain the integrity and discoverability of your command-line interface.

Quick Start

Verify the command entrypoint for the demo command module.

Frequently Asked Questions about rules-cmd

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

FAQPage Schema

How do I validate command entrypoints in the cmd directory?▼

To validate command entrypoints, you check that bootstrap files within the cmd/ directory remain thin, focusing strictly on parsing and dispatching, while ensuring their package wiring is properly structured and consistently named.

How do I keep CLI command paths consistent with directory structures?▼

Keeping CLI command paths consistent involves enforcing naming rules that align command names directly with their directory structures, preventing ambiguity and improving the discoverability of your command-line interface.

How do I anchor command-line documentation to actual command files?▼

Anchoring command-line documentation requires verifying that references and documentation paths point directly to actual command files, ensuring that modifications to CLI wrappers maintain accurate and discoverable docs.

What are thin command entrypoints and when do I need them?▼

Thin command entrypoints are bootstrap files that focus strictly on parsing and dispatching rather than business logic. You need them when adding or modifying command-line tools to maintain structural integrity.

Do I need external dependencies to validate command bootstrap files?▼

You do not need external dependencies to validate command bootstrap files. The validation logic operates independently using internal scripts and references to check package wiring and command-path documentation.