ores-cli-recipes

To keep CLI documentation synced with command changes, compare source entity parsers against documented recipes to identify discrepancies and generate updated recipe blocks with accurate option names.

The best way to update CLI recipes when options are renamed is to diff the parser definitions with the recipe documentation, ensuring the documented option names match the current source of truth.

To validate CLI recipes against parser definitions, run a diff comparing the command parsers with the recipe documentation to detect missing commands or mismatched option names and produce corrections.

You need to regenerate CLI recipe documentation when new commands are added or existing commands change across the CLI, ensuring the documentation reflects the current implemented command set.

Yes, CLI recipe synchronization works without external dependencies, directly comparing internal project entity parsers with the recipe documentation to output updated blocks.

CLI recipe documentation shows outdated option names when the source code parsers have been updated but the documentation has not been synchronized to reflect the current command definitions.