Skip to main content

QZX in action

From a problem
to a useful answer.

Explore a project, investigate disk space or inspect an HTTP response. See what each command reveals and choose the next step.

Read-only checksVerifiable capturesHuman output and JSON

What do you need to investigate?

Three everyday tasks that show how QZX works.

A URL that fails

Read the HTTP status and distinguish a server response from an available page.

Inspect the response

01 / Projects

Understand the project before you edit.

Technologies, dependencies and findings in one briefing. Discovered tests and lint checks keep their actual status: configured, not run.

Try it from a project root
qzx diagnoseProject . --json
What QZX found
Technology
Python
Unique packages
1
Findings
1

Declared dependencies httpx

Captured from a small test project. The inspection did not run its tests or linter.

View JSON excerpt
{
    "success": true,
    "details": {
        "technologies": [
            "Python"
        ],
        "dependencies": {
            "unique_declared_package_count": 1,
            "unique_packages": [
                "httpx"
            ]
        },
        "version_control": {
            "status": "not_repository"
        },
        "file_scan": {
            "scanned_file_count": 3,
            "scan_complete": true
        },
        "summary": {
            "issue_count": 1,
            "verification": {
                "release_readiness": "not_assessed"
            }
        },
        "validation": {
            "tests": {
                "status": "configured_not_run"
            },
            "lint": {
                "status": "configured_not_run"
            }
        }
    }
}

02 / Storage

See what is taking up space.

Check volume capacity and list large files and verified duplicates. The diagnosis leaves files in place so you can decide what to do.

Try it in the folder you want to inspect
qzx diagnoseStorage . --min-file-size 1KB --max-files 10 --duplicate-min-size-kb 1 --max-depth 2 --json
Space to investigate
Used
99.4%
Free
19.85 GB
Duplicate groups
1

Captured from a bounded test folder; capacity belongs to its containing volume. No files were deleted.

View JSON excerpt
{
    "success": true,
    "read_only": true,
    "partial": false,
    "scan_scope": {
        "max_depth": 2,
        "large_file_min_size": "1KB"
    },
    "assessment": {
        "capacity_status": "critical",
        "percent_used": 99.4,
        "free_readable": "19.85 GB",
        "duplicate_groups": 1,
        "confirmed_reclaimable_bytes": 9984,
        "reclaimable_space_basis": "logical_content_bytes",
        "physical_reclaimable_bytes": null
    }
}

03 / HTTP

Find out what the URL returns.

Separate command completion from the HTTP result. In this capture, the request completed and the server returned a 404.

Try a public URL
qzx checkUrlStatus https://example.com 10 --json
A 404 response, with context
HTTP status
404
Check
Completed
Requested resource
Not found

This 404 was captured from a local test HTTP server. The copyable command queries example.com and will receive its own response.

View JSON excerpt
{
    "success": true,
    "is_online": false,
    "status_code": 404
}

Try it in your terminal

Pick a problem. Start with a command.

Install the published QZX release and run a read-only check in your own environment.

python -m pip install --upgrade qzx
Installation options
Where these results come from

Captured on 2026-10-08 with QZX 0.2.2.0.15, CPython 3.13.13 and Windows 11 10.0.26200.

These figures belong to the recorded examples. Copyable commands run in your terminal and their results depend on the environment.