dev-cli-consistency-audit

A CLI consistency audit analyzes top-level and subcommand help outputs to surface naming and formatting inconsistencies in argument naming, flag conventions, and help text. It generates a report identifying interface alignment gaps.

CLI documentation alignment verifies that README examples and command usage reflect actual CLI behavior. It compares implemented command definitions against documentation to detect usage pattern drift and formatting mismatches.

Yes, you can run a CLI consistency audit as part of a release workflow to catch regressions in command definitions and usage patterns. It validates help outputs and frontmatter metadata compliance before release.

Yes, the CLI consistency audit applies to both single-command and multi-command CLIs across development, testing, and release workflows. It evaluates argument naming and flag conventions regardless of command structure complexity.

The best way to fix help text inconsistencies is running an audit that enforces frontmatter-based metadata compliance for name, description, and compatibility, then validating CLI help outputs against README documentation and implementation.

CLI documentation drifts from implementation when command definitions change without updating README examples. A consistency audit detects this by validating that CLI help outputs and README documentation align with the actual implementation behavior.