CQ - Python Code Quality Analysis Tool
Run 12 code quality tools, aggregate results into one score, and surface the single most critical defect as a focused markdown prompt — ready to pipe to any LLM.
This can dramatically reduce the amount of noise for LLMs (and humans) and remove the need for them to know about these tools.
Note: It never edits your files. This is a job for you or an LLM. You may wish to run ruff check --fix and ruff format first.
cq check . -o llm # top defect as markdown, pipe to an LLM
cq check . # table overview of all scores
cq check . -o score # numeric score only, exits 1 on errors (CI gate)
Install
# install the `cq` command line tool from PyPi
uv tool install python-code-quality
# or, clone it then install
git clone https://github.com/rhiza-fr/py-cq.git
cd py-cq
uv tool install .
Tools
These tools are run in parallel except:
When running '-o llm', we run sequentially and exit early at the first error.
coverage is a special case: it starts alongside pytest and is cancelled if
pytest fails, scoring 0% without a second test run.
| Order | Tool | Measures |
|---|---|---|
| 1 | compileall | Syntax errors |
| 2 | ruff | Lint / style |
| 3 | ty | Type errors |
| 4 | bandit | Security vulnerabilities |
| 5 | pytest | Test pass rate |
| 6 | coverage | Test coverage |
| 7 | vulture | Dead code |
| 8 | interrogate | Docstring coverage |
| 9 | radon cc | Cyclomatic complexity |
| 10 | radon mi | Maintainability index |
| 11 | radon hal | Halstead volume / bug estimate |
| 12 | ruff format | Formatting (fraction of files already formatted) |
Diskcache is used to cache tool output for lightning fast re-runs. Sane defaults: <100 Mb, <5 days, No pickle risk.
Usage
cq check . # Table overview of scores for humans
cq check . -o llm # Top defect as markdown for LLMs
cq check . -o llm-json # Top defect as JSON with fingerprint (for automation)
cq check . -o score # Numeric score only for CI
cq check . -o json # Detailed parsed JSON output for jq
cq check . -o raw # Raw tool output for debug
cq check path/to/file.py # Just one file (skips pytest and coverage)
cq check . --only ruff,ty # Run only specific tools
cq check . --skip bandit # Skip specific tools
cq check . --exclude demo # Exclude paths from all tools
cq check . --workers 1 # Run sequentially if you like things slow
cq check . --clear-cache # Clear cached results before running (rarely needed)
cq check . -o llm --hint # Append "run cq again to verify" (for human workflows)
cq config --path path/to/project/ # Show effective tool configuration
cq is-fixed <fingerprint> # Check whether a specific issue has been resolved
Exit codes: cq check exits with code 1 if any tool metric falls below its error_threshold, making it suitable as a CI gate:
cq check . && deploy # block deploy on errors
cq check . -o score # print score, exit 1 on errors
Fingerprint-based verification
-o llm-json returns a JSON object with a stable id fingerprint you can pass back to cq is-fixed to check whether a specific issue has been resolved — without re-running all tools:
# Get the top defect as JSON
cq check . -o llm-json
{
"id": "ruff::my-project::src/foo.py::42::E501",
"file": "src/foo.py",
"project": "/home/user/my-project",
"message": "..."
}
# After fixing, verify only that issue (fast — reruns one tool on one file)
cq is-fixed "ruff::my-project::src/foo.py::42::E501"
This is most useful in automation: fix an issue, confirm it's gone, then fetch the next one. Note that this only verifies the original issue is no longer present — a full project-wide scan is still needed to guarantee no regressions, assuming you have sufficient tests.
Python Library
py_cq can be used as a library — no subprocess required. Instantiate CQ with a project root; config is loaded once from pyproject.toml.
from py_cq import CQ
cq = CQ(".") # load config from ./pyproject.toml
cq = CQ(".", skip=["bandit"]) # skip specific tools
cq = CQ(".", only=["ruff", "ty"]) # run only specific tools
cq = CQ(".", workers=4) # control parallelism
Methods mirror the CLI and return data objects:
# list[ToolResult] — all parsed results before aggregation (-o raw / -o json)
results = cq.raw()
# CombinedToolResults — aggregated score and per-tool results (-o score / table)
combined = cq.check()
print(combined.score) # float
print(combined.tool_results) # list[ToolResult]
# dict — top defect as JSON, equivalent to -o llm-json
issue = cq.check_llm_json()
issue["id"] # fingerprint: "ruff::project::src/foo.py::42::E501"
issue["file"] # "src/foo.py"
issue["message"] # markdown prompt ready to send to an LLM
issue["project"] # absolute project root path
# bool — True if the fingerprinted issue is gone
# Reruns only the affected tool on the affected file — much faster than a full check.
# Pass the id from check_llm_json; also available as `cq is-fixed <id>` on the CLI.
fixed = cq.is_fixed(issue["id"])
check_llm_json accepts the same options as cq check . -o llm-json:
issue = cq.check_llm_json(limit=3, silence=["src/generated.py"], hint=True)
Typical automation loop:
from py_cq import CQ
cq = CQ(".")
while True:
issue = cq.check_llm_json()
if issue["id"] is None:
break # all clear
fix(issue["message"]) # call your LLM
assert cq.is_fixed(issue["id"])
Claude Code Integration
Add a stop hook to your project's .claude/settings.json so Claude automatically checks quality after each session and loops until clean:
{
"hooks": {
"Stop": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "cq check . -o score && echo 'CQ: all clear' || cq check . -o llm; true"
}
]
}
]
}
}
When the score passes, Claude sees CQ: all clear (~5 tokens). When it fails, Claude receives the targeted fix prompt and continues working. This automates the cq check . -o llm | claude -p "fix this" loop.
Note: Use project-level
.claude/settings.json, not global settings — this hook only makes sense in Python projects.
As a slash command (skill)
For manual invocation, create .claude/commands/cq-fix.md:
$(cq check . -o llm)
Then invoke it with /cq-fix in Claude Code. The $(...) embeds the live cq output directly into the prompt before Claude starts, so it sees the issue immediately without an extra tool call.
Hook vs skill:
- Stop hook — automatic, runs after every session, best for unattended loops
- Skill — manual
/cq-fix, gives you explicit control over when to check
Table output
> cq check .
┏━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━━┓
┃ Tool ┃ Time ┃ Metric ┃ Score ┃ Status ┃
┡━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━━┩
│ compile │ 0.42s │ compile │ 1.000 │ OK │
│ ruff │ 0.17s │ lint │ 1.000 │ OK │
│ ty │ 0.33s │ type_check │ 1.000 │ OK │
│ bandit │ 0.56s │ security │ 1.000 │ OK │
│ pytest │ 0.91s │ tests │ 1.000 │ OK │
│ coverage │ 1.26s │ coverage │ 0.910 │ OK │
│ vulture │ 0.32s │ dead_code │ 1.000 │ OK │
│ interrogate │ 0.36s │ doc_coverage │ 1.000 │ OK │
│ radon-cc │ 0.32s │ simplicity │ 0.982 │ OK │
│ radon-mi │ 0.38s │ maintainability │ 0.869 │ OK │
│ radon-hal │ 0.30s │ file_bug_free │ 0.928 │ OK │
│ radon-hal │ │ file_smallness │ 0.851 │ OK │
│ radon-hal │ │ functions_bug_free │ 0.913 │ OK │
│ radon-hal │ │ functions_smallness │ 0.724 │ OK │
│ ruff-format │ 0.12s │ formatted │ 1.000 │ OK │
│ │ │ Score │ 0.965 │ │
└──────────────────┴──────────┴───────────────────────────┴─────────┴──────────┘
Single score output
> cq check . -o score
0.9662730667181059 # this is designed to approach but not reach 1.0
Json output
> cq check . -o json
[
{
"tool_name": "compile",
"metrics": {
"compile": 1.0
},
"details": {},
"duration_s": 0.05611889995634556
}
...
]
Raw output
> cq check . -o raw
[
{
"tool_name": "compile",
"command": "D:\\ai\\py-cq\\.venv\\Scripts\\python.exe -m compileall -r 10 -j 8 . -x .*venv",
"stdout": "",
"stderr": "",
"return_code": 0,
"timestamp": "2026-02-20 10:01:22"
}
...
]
Both json and raw output pipe cleanly to jq:
# Get the coverage section
cq check . -o raw | jq '.[] | select(.tool_name == "coverage")'
# Get parsed coverage metrics only
cq check . -o json | jq '.[] | select(.tool_name == "coverage") | .metrics'
Configuration
Add a [tool.cq] section to your project's pyproject.toml:
[tool.cq]
# Skip tools that are slow or not relevant to your project
disable = ["coverage", "interrogate"]
# Exclude paths from all tools (merged with --exclude CLI flag)
exclude = ["demo", "docs"]
# Lines of source context shown around each defect in LLM output (default: 15)
context_lines = 15
# Override warning/error thresholds per tool
[tool.cq.thresholds.coverage]
warning = 0.9
error = 0.7
Tool IDs match the keys in src/py_cq/config/config.toml: compile, ruff, ty, bandit, pytest, coverage, radon-cc, radon-mi, radon-hal, vulture, interrogate, ruff-format.
Default config
Defined in src/py_cq/config/config.toml (sections are namespaced by language):
[python.compile]
command = "{python} -m compileall -r 10 -j 8 \"{context_path}\" -x .*venv|\\.claude"
parser = "CompileParser"
order = 1
warning_threshold = 0.9999
error_threshold = 0.9999
cache_invariant = "ast"
[python.ruff]
command = "{python} -m ruff check --output-format concise --no-cache \"{context_path}\" --exclude .claude{exclude}"
exclude_format = " --exclude {path}"
parser = "RuffParser"
order = 2
warning_threshold = 0.9999
error_threshold = 0.9
[python.ty]
command = "{python} -m ty check --output-format concise --color never \"{context_path}\" --exclude .claude{exclude}"
exclude_format = " --exclude {path}"
parser = "TyParser"
order = 3
warning_threshold = 0.9999
error_threshold = 0.8
run_in_target_env = true
extra_deps = ["ty"]
[python.bandit]
command = "{python} -m bandit -r {scan_targets} -f json -q -s B101 --severity-level medium{exclude}"
scan_exclude_names = [".venv", ".claude", "tests"]
exclude_format = " --exclude {abs_native_path}"
parser = "BanditParser"
order = 4
warning_threshold = 0.9999
error_threshold = 0.8
[python.pytest]
command = "{python} -m pytest -vv \"{context_path}\" --ignore .claude{exclude}"
exclude_format = " --ignore {path}"
parser = "PytestParser"
order = 5
warning_threshold = 1.0
error_threshold = 1.0
run_in_target_env = true
extra_deps = ["pytest"]
skip_for_file = true
cache_invariant = "ast"
[python.coverage]
command = "{python} -m coverage run --omit=*/tests/*,*/test_*.py -m pytest \"{context_path}\" --ignore .claude{exclude} && {python} -m coverage report --show-missing --omit=*/tests/*,*/test_*.py"
exclude_format = " --ignore {path}"
parser = "CoverageParser"
order = 6
warning_threshold = 0.9
error_threshold = 0.5
run_in_target_env = true
extra_deps = ["coverage", "pytest"]
skip_for_file = true
skip_if = "pytest"
cache_invariant = "ast"
[python.vulture]
command = "{python} -m vulture \"{context_path}\" --min-confidence 80 --exclude .venv,dist,.*_cache,docs,.git,.claude{exclude}"
exclude_format = ",{path}"
parser = "VultureParser"
order = 7
warning_threshold = 0.9999
error_threshold = 0.8
cache_invariant = "ast"
[python.interrogate]
command = "{python} -m interrogate \"{context_path}\" -e .claude{exclude} -v --fail-under 0"
exclude_format = " -e {path}"
parser = "InterrogateParser"
order = 8
warning_threshold = 0.8
error_threshold = 0.5
[python.interrogate.parser_config]
skip_empty_init = true
[python.radon-cc]
command = "{python} -m radon cc --json --exclude '.claude/**' \"{context_path}\""
parser = "ComplexityParser"
order = 9
gate_strict = false
warning_threshold = 0.6
error_threshold = 0.4
[python.radon-mi]
command = "{python} -m radon mi -s --json --exclude '.claude/**' \"{context_path}\""
parser = "MaintainabilityParser"
order = 10
gate_strict = false
warning_threshold = 0.6
error_threshold = 0.4
[python.radon-hal]
command = "{python} -m radon hal -f --json --exclude '.claude/**' \"{context_path}\""
parser = "HalsteadParser"
order = 11
gate_strict = false
warning_threshold = 0.35
error_threshold = 0.3
[python.ruff-format]
command = "{python} -m ruff format --check --output-format concise --no-cache \"{context_path}\" --exclude .claude --config \"include=['*.py','*.pyi','*.ipynb']\"{exclude}"
exclude_format = " --exclude {path}"
parser = "RuffFormatParser"
order = 12
gate_strict = false
warning_threshold = 0.9999
error_threshold = 0.5
Respect
Many thanks to all the wonderful maintainers of :
Metadata
Release files for python-code-quality 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| python_code_quality-0.3.1.tar.gz | 58.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| python_code_quality-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 132.6 kB
Release files / python_code_quality-0.3.1.tar.gz
| Download URL | python_code_quality-0.3.1.tar.gz |
|---|---|
| Size | 58.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b5ae4b709e5aeb2788a383a3a8ff33ac8679241b72d38df80a1df954377c5e83
|
|
BLAKE2b-256 checksum How to use checksums |
fc1700e421d496ccd7834fbd368241c8e6153bac51474722b9436a4d84ea1204
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency logRelease files / python_code_quality-0.3.1-py3-none-any.whl
| Download URL | python_code_quality-0.3.1-py3-none-any.whl |
|---|---|
| Size | 73.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09e8b7d1ff25b2d35f0db61b67798eecf230caa0ff97fbddb21a5a898128e84b
|
|
BLAKE2b-256 checksum How to use checksums |
a5f8a4bd3578ccb548893200e21ac5eef6929f7a1b47a2866e5ad0aaf66647c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency log