parsearger-utils_skill

Overview

This skill provides utilities for working with parseArger-based CLIs: project scaffolding, documentation generation, bash completion, HTML form generation, and bulk operations. Use it to bootstrap a CLI project, produce user-facing docs, emit completion scripts, create web forms that map to CLI arguments, and perform batch edits across many scripts. It integrates with external tools like the completely gem or Docker when needed.

How this skill works

The utilities inspect parseArger argument definitions in script files or directories and generate outputs (files, YAML, HTML, or completion scripts) accordingly. Invocation prefers a system-wide parseArger binary if present, otherwise it falls back to a local ./parseArger in the project root. Commands accept file and directory inputs, output targets, and flags that control runtime behavior such as running the completion generator or emitting JS for web forms.

When to use it

• Starting a new CLI project and needing a full scaffold with subcommands, tests, and docs.
• Generating Markdown usage documentation from existing script argument definitions.
• Producing bash completion scripts for complex tools using the completely library or Docker.
• Creating a standalone HTML form so non-technical users can build command lines in a browser.
• Applying bulk edits like version bumps across many scripts or directories.

Best practices

• Always run which parseArger or ensure a local ./parseArger is present before invoking commands.
• Keep argument definitions in the executable scripts so document and completion tools can source them.
• When generating completions, prefer a native completely gem install or provide a Docker-based --completely-cmd.
• Use --subcommand-directory to include dynamically discovered subcommands in completion output.
• Review generated YAML or HTML before auto-deploying; use --no-run-completely to produce YAML only for inspection.

Example use cases

• Bootstrap a new CLI named mytool with article and deploy subcommands and an initial documentation.md.
• Generate a completely.bash completion script for ./bin/my-tool by scanning the bin directory for subcommands.
• Document all scripts in ./bin into DOCUMENTATION.md by running the document command on the directory.
• Create form.html that maps my-script arguments to an interactive web form with JS-enabled command building.
• Bump the version string to 2.0.0 across multiple scripts by running bulk-parse with --bump and multiple --file flags.