rules-cmd

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.

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.

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.

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.

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.