@spec-this/cli

//force update

Official CLI tool for the Spec-This code intelligence platform.

Debug Mode

The CLI includes comprehensive debug logging to help troubleshoot issues, especially with API calls.

$3

You can enable debug logging in several ways:

1. Using the --debug flag:
``bash
spec-this scan --debug
`

2. Using the --log-level flag:
`bash
spec-this scan --log-level debug
`

3. Using environment variables:
`bash
export SPEC_THIS_DEBUG=true
spec-this scan
`

Or:
`bash
export SPEC_THIS_LOG_LEVEL=debug
spec-this scan
`

4. For a single command:
`bash
SPEC_THIS_DEBUG=true spec-this scan
`

$3

Available log levels (from most to least verbose):
- trace - Very detailed trace information
- debug - Detailed debug information (includes all API calls and responses)
- info - General informational messages (default)
- warn - Warning messages
- error - Error messages
- fatal` - Application crashes

$3

When debug mode is enabled, you'll see:
- Every API request with method, endpoint, URL, and authentication status
- Request body size and preview (for POST/PUT requests)
- Response status, timing, and preview
- Detailed error information including 413 errors with payload size
- Batch splitting information (when scan data is split into batches)
- Scan statistics (file counts, symbol counts, etc.)

$3

If you're getting 413 (Payload Too Large) errors, debug mode will show:
- The exact size of the request that failed
- Whether batching is being used
- How many batches are being sent and their sizes

This information can help determine if the batch size needs to be reduced or if there's an issue with the API server configuration.