Claude Code CLI commands

Reproducible practice

Turn a one-off repository inventory into machine-checkable output

Use print mode for a bounded read-only question, cap tool access, preserve the response, and validate its transport format.

Prerequisites

• A trusted repository and valid authentication.
• jq or another JSON parser available locally.
• An understanding that print mode can incur usage and skips the interactive workspace trust dialog.

Steps

1. Confirm the flags on the installed version

   Help output is the local source of truth for spelling and accepted values.

   claude --version
   claude --help

2. Run a read-only inventory

   The prompt asks for evidence, while tools and plan mode constrain the execution surface.

   claude -p "List build and test commands with the file that defines each one." \
     --permission-mode plan \
     --allowedTools "Read" "Grep" "Bash(git status --short)" \
     --output-format json > /tmp/claude-inventory.json

3. Validate the envelope

   A parseable response proves the CLI transport, not the factual accuracy of every model statement.

   jq -e . /tmp/claude-inventory.json >/dev/null

4. Verify cited commands in repository files

   Open the cited package, build, or CI files and compare command spellings before using the inventory.

Expected result

The command exits, writes valid JSON, and produces a source-linked inventory that can be checked against repository files.

Validation

• Require a zero exit status and valid JSON.
• Verify each reported command against its cited file.
• Do not treat model prose as proof that a command succeeded.

Failure handling

Cleanup or rollback

• Delete the temporary JSON after review.
• If the command touched files unexpectedly, stop and inspect git status before any cleanup.

Boundaries and when not to use it

• Print mode is suitable for bounded automation, not interactive clarification-heavy work.
• Allowed tools auto-approve matching tools; use --tools when the goal is to remove other tools from availability.