development · Command reference
qzx analyzeComplexity
What it does
Analyzes code complexity metrics for files or projects
Command maturity: Alpha
Available for real use and feedback while its interface and behavior can still evolve. This is the current development-checkout assessment. Every future immutable release tag preserves the exact assessment shipped by that version. Available in PyPI 0.2.2.0.8. This page documents the 0.2.2.0.8 alpha development checkout.
Behavior and built-in protections
Inspects without changing state
Direct execution for this operation
Works without invoking native programs
Works without network access
No elevation required by design
This safety classification was reviewed by OpenAI GPT-5.6 Pro against implementation digest sha256:5f60fc934b7c21909d9f3d624a6158dc72026d496d3b0f92aad71385ef146b66 on 2026-08-25.
Exact syntax
qzx analyzeComplexity <file_path> [recursive] [detail_level] --jsonParameters
Swipe or use the horizontal scrollbar to see every column.
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| file_path | str | Yes | Not declared | Path to the file or directory to analyze |
| recursive | bool | No | false | Whether to recursively analyze directories: -r/--recursive for unlimited, -rN/--recursiveN for N levels |
| detail_level | str | No | "detailed" | Detail level: "detailed" or "summary" |
Input examples
qzx analyzeComplexity "main.py"Analyze complexity of a single Python file
qzx analyzeComplexity "src/components" -rRecursively analyze all code files in a directory
qzx analyzeComplexity "project/" -r2 --detail-level summaryGenerate a summary report analyzing up to 2 levels deep
For the complete structured payload, add --json: qzx analyzeComplexity <file_path> [recursive] [detail_level] --json
Representative output example
This illustrative JSON is derived from the current implementation-backed result contract. It shows what the command can return without claiming a recorded execution; values vary with inputs, host, permissions, and optional tools.
Example command: qzx analyzeComplexity "main.py" --json
{
"success": true,
"message": "Analyzes code complexity metrics for files or projects. In this illustrative example, the command completed successfully.",
"meta": {
"command": "analyzeComplexity",
"command_maturity": {
"stage": "alpha",
"label": "Alpha",
"sequence": 2,
"public_executable": true,
"stability": "interface_may_change",
"summary": "Available for real use and feedback while its interface and behavior can still evolve.",
"promotion_review_required": false,
"assessment_scope": "development_checkout"
},
"duration_ms": 0,
"schema_version": 1
},
"details": {
"path": "C:\\project\\example.txt",
"files_seen": "C:\\project\\example.txt",
"files_analyzed": "C:\\project\\example.txt",
"detail_level": "Example value",
"analyses": [
{
"name": "example",
"status": "ok"
}
]
},
"report": "Analysis complete.\nNo blocking issues were found."
}View the JSON result contract
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"required": [
"success",
"message",
"meta"
],
"properties": {
"success": {
"type": "boolean"
},
"message": {
"type": "string"
},
"meta": {
"type": "object",
"required": [
"command",
"command_maturity",
"duration_ms",
"schema_version"
],
"properties": {
"command": {
"type": "string"
},
"command_maturity": {
"type": "object",
"required": [
"stage",
"label",
"sequence",
"public_executable",
"stability",
"summary",
"promotion_review_required",
"assessment_scope"
],
"properties": {
"stage": {
"type": "string"
},
"label": {
"type": "string"
},
"sequence": {
"type": "integer"
},
"public_executable": {
"type": "boolean"
},
"stability": {
"type": "string"
},
"summary": {
"type": "string"
},
"promotion_review_required": {
"type": "boolean"
},
"assessment_scope": {
"type": "string"
},
"note": {
"type": "string"
},
"review": {
"type": "object",
"required": [
"reviewed_on",
"rationale",
"evidence"
],
"properties": {
"reviewed_on": {
"type": "string",
"format": "date"
},
"rationale": {
"type": "string"
},
"evidence": {
"type": "array",
"minItems": 1,
"items": {
"type": "string"
}
},
"replacement": {
"type": "string"
}
},
"additionalProperties": false
}
},
"additionalProperties": true
},
"duration_ms": {
"type": "number"
},
"schema_version": {
"type": "integer"
}
},
"additionalProperties": true
},
"details": {
"oneOf": [
{
"type": "object",
"properties": {
"path": [],
"files_seen": [],
"files_analyzed": [],
"detail_level": [],
"analyses": []
},
"additionalProperties": true
},
{
"type": "object",
"properties": {
"path": [],
"detail_level": []
},
"additionalProperties": true
},
{
"type": "object",
"properties": {
"path": [],
"files_seen": [],
"files_analyzed": {
"type": "integer"
},
"supported_extensions": []
},
"additionalProperties": true
}
]
},
"error": {
"type": "string"
},
"error_code": {
"type": "string"
},
"report": []
},
"additionalProperties": true
}Errors and limits
The public contract requires success=false and a descriptive message on failure. This catalog does not yet declare a command-specific error taxonomy; inspect the result and do not invent error codes.
QZX is alpha software. Optional dependencies, permissions, and host capabilities can change the result.
Evidence workflow: ready for deterministic automated capture.
Evidence and provenance
- Implementation
- src/qzx/commands/development/analyze_complexity.py
- Tests
- No command-specific test file with the same module name was found; this does not prove that all coverage is absent.
- Documentation channel
- Development documentation 0.2.2.0.8 · main · sha256:9aa902dfb6b006017e52972bf7871fef49b03ec24ff80741231d743d0354bfc2
- Availability
- 0.2.2.0.8 or earlier
Keep exploring
Related commands
These commands also belong to the development category. Compare them to choose the operation that best fits your task.
qzx addPythonDocstringsPreviews or adds generated docstring templates to functions, methods, and classes in one Python fileqzx auditRepositoryRuns security and quality audits on a Git repository (secrets, large files, duplicates, .gitignore compliance, licenses)qzx traceEnvVarTraces usage of an environment variable across code files, .env, and .env.example templatesqzx cleanDevelopmentArtifactsFinds development caches, dependency directories, and generated build artifacts; preview is the default