add-python-command

To add a Python CLI subcommand using argparse subparsers, you must follow a four-way update workflow: implement the command logic, wire the parser, update the dispatch function, and write tests. This ensures consistent CLI behavior and test coverage.

Updating an existing Python CLI subcommand involves modifying the implementation, adjusting the argparse parser wiring, updating the dispatch logic, and expanding the test suite. This workflow preserves existing style and maintains hermetic testing standards for the CLI project.

Yes, writing tests is required when adding an argparse subcommand to ishlib. The process mandates a hermetic testing setup and structured review of CLI changes, ensuring new subcommands conform to the project's established testing strategy and maintain coverage.

The best way to ensure consistent dispatch logic across Python CLI subcommands is to use a structured four-way update workflow. This approach standardizes implementation, parser wiring, dispatch routing, and testing, conforming to established argparse subparsers patterns and project guidelines.

The four-way update workflow for Python CLI tools operates by sequentially addressing implementation, parser wiring, dispatch, and tests. It ensures that adding or updating subcommands aligns with existing argparse patterns and project-specific configuration guidelines like CLAUDE.md.

Yes, you can update ishlib CLI subcommands without breaking existing argparse parser configurations by following the prescribed workflow. It carefully integrates updates into the parser wiring and dispatch logic while preserving the original style and test coverage.