Appendix B: Command Reference

This appendix is generated from the binary, not written by hand. Every command path below was read out of pmat 3.32.0’s own --help output and then re-checked by running pmat <path> --help and requiring exit status 0. Nothing in the tables is transcribed from memory. Regenerate it with:

python3 scripts/gen-appendix-b.py > src/appendix-b-commands.md

If you bookmarked this page before 2026-08-25, what you read here was wrong. Earlier editions listed 31 top-level commands that pmat has never had — pmat architecture, pmat rules, pmat clippy, pmat status, pmat scan, pmat dashboard and more. Of the 150 command paths that edition printed, 73 did not resolve. Every one of them is accounted for in Commands earlier editions listed that do not exist, with the real replacement where there is one.

pmat 3.32.0 exposes 70 top-level commands and 202 subcommands.

How to read this appendix

• Aliases are real. pmat a cx is pmat analyze complexity. Anything in the Aliases column can be substituted for the command name.

• --help works at every level, and short-circuits before argument validation: pmat <command> --help and pmat <command> <subcommand> --help always print and exit 0 if the path exists. That is exactly the check this appendix is built on.

• A command with subcommands requires one. pmat analyze . is not “analyze the current directory” — it exits 2 with error: unrecognized subcommand. The path goes to the subcommand: pmat analyze complexity --path .

• Path arguments are not uniform, and this is the single most common mistake. Some commands take a positional path, some take --path, some take --project-path, and passing a positional to a command that wants a flag exits 2 with error: unexpected argument found. The tables below name the form for every command, so check the column rather than guessing:

  pmat tdg .                              # positional
  pmat analyze complexity --path .        # --path
  pmat quality-gate --project-path .      # --project-path
  

• [NOT AVAILABLE in the default build] in a description is pmat’s own wording. Those commands parse and appear in --help, but the shipped cargo install pmat binary refuses them at runtime; they need a non-default --features build. They are marked ⚠ below.

Top-level commands

Commands that take no subcommand

These run directly. The Path column is the form this command accepts a target path in — using the wrong one exits 2.

A — in the Path column means the command takes no path at all, or takes its target some other way. Two that catch people out: pmat extract takes its file as the value of --list (pmat extract --list src/main.rs), and pmat generate takes a template category and name (pmat generate makefile rust/cli -p project_name=demo).

Subcommands by parent

pmat scaffold (aliases: sc)

Scaffold complete project or agent

pmat analyze (aliases: a an)

Analyze code metrics and patterns

pmat qdd (aliases: qd)

Quality-Driven Development (QDD) tool for creating and refactoring code with guaranteed quality

pmat red-team (aliases: rt hallucination-detect)

Red Team Mode: Automated hallucination detection for commits and code

pmat org (aliases: organization)

[NOT AVAILABLE in the default build] Organizational intelligence — needs –features org-intelligence

pmat mcp

Connect pmat to an MCP client: every transport, in one place

pmat agy (aliases: antigravity)

Google Anti-Gravity customizations translator

pmat prompt (aliases: p)

AI prompt generation (defect-aware, ticket-based, spec-based)

pmat enforce (aliases: enf)

Enforce extreme quality standards using state machine

pmat refactor (aliases: ref rf)

Refactor code with real-time analysis or interactive mode

pmat roadmap (aliases: road rm)

Roadmap management with PDMT todos and quality gates

pmat memory

Memory management and optimization

pmat cache

Cache strategy management and optimization

pmat agent (aliases: ag)

[NOT AVAILABLE in the default build] Claude Code background agent — needs –features agent-daemon

pmat tdg (aliases: grade debt-grade)

Grade technical debt and code quality (TDG - Technical Debt Grading)

pmat quality-gates (aliases: gates qg)

Run configurable quality gates on the current project

pmat maintain (aliases: maint m)

Project maintenance commands (cleanup, validation, reports)

pmat hooks (aliases: hook h)

Pre-commit hook management and installation

pmat embed (aliases: emb)

Manage semantic search embeddings for code search

pmat semantic (aliases: sem find-code)

Semantic code search using embeddings

pmat debug (aliases: dbg)

Time-travel debugging commands for execution traces

pmat work (aliases: w)

Unified GitHub/YAML workflow management

pmat qa-work (aliases: qa quality)

QA validation after work completion with Toyota Way quality gates

pmat oracle (aliases: fix pdca)

PMAT Oracle - PDCA loop for automated quality improvement (Toyota Way) Converges ANY Rust project toward perfect quality using CITL signals

pmat spec (aliases: specification)

Specification management and validation

pmat comply (aliases: compliance)

PMAT compliance checking and migration system (runs check by default)

pmat test-discovery (aliases: test-fix fix-tests)

Systematic test discovery and fixing

pmat cuda-tdg (aliases: gpu-tdg simd-tdg)

CUDA-SIMD Technical Debt Gradient (100-point Popper falsification scoring) Analyzes CUDA PTX, SIMD (AVX2/AVX-512/NEON), and WGPU code for defects Integrates Toyota Production System principles with falsificationist methodology

pmat stack (aliases: stk)

Cross-repo dependency coordination for the sovereign AI stack

Verified examples

Each block below was executed against pmat 3.32.0 on 2026-08-25, in a two-file Rust fixture, and the exit status recorded. Output is trimmed for length; nothing else is edited.

pmat --version
# pmat 3.32.0                                                     exit 0

pmat analyze complexity --path .
# ✅ Successfully analyzed 1 file(s)
#   Files analyzed: 1
#   Total functions: 3                                            exit 0

pmat analyze satd --path .
# Found 1 SATD violations in 1 files (analysed 1 of 1 file(s) walked)   exit 0

pmat analyze dead-code --path .
#   Files with dead code: 1
#   Dead code percentage: 27.8%                                   exit 0

pmat analyze tdg -p . --format table
#   Average Score: 99.5/100 (A+)                                  exit 0

pmat tdg .
#   Overall Score: 99.5/100 (A+)                                  exit 0

pmat quality-gate -p . --checks complexity
# Quality Gate: PASSED
# Total violations: 0                                             exit 0

pmat analyze dag --target-nodes 10
# 📊 full-dependency: rendered 4 nodes and 0 edges
# graph TD                                                        exit 0

pmat extract --list src/main.rs
# { "file": "src/main.rs", "language": "rust", "items": [ ...     exit 0

pmat search rust --limit 2
#  1. template://readme/rust/cli (score: 9.00)                    exit 0

pmat mcp connect
# prints every way to connect this binary to an MCP client, with
# the exact `claude mcp add` line                                 exit 0

Two failures worth knowing, also executed. They are shown as a table rather than a code block on purpose: this is what a wrong form looks like, not something to type.

Between them these two shapes account for most broken pmat lines in circulation. Check the Path column in the tables above before typing a path.

Commands earlier editions listed that do not exist

Every row here was printed as a working command by this appendix before 2026-08-25. None of them resolve against pmat 3.32.0. The middle column is what the binary actually does when you type it; the right column is the nearest real command, verified to resolve.

Where the right column says nothing — there is no equivalent. pmat has no plugin system, no webhook manager, no notification sender, no team/retrospective features and no secret scanner. That capability was never built; it was only ever written down.

Global options

These are accepted by every command (from pmat --help):

--format and --output are per-command, not global: most analysis commands take -f, --format and -o, --output, but the accepted values differ per command. Check pmat <command> --help.

Environment variables

Only variables that pmat 3.32.0 itself declares in --help (as [env: NAME=]) or prints from pmat mcp connect are listed. Earlier editions of this appendix listed eight variables — PMAT_CONFIG_PATH, PMAT_PROFILE, PMAT_MAX_THREADS, PMAT_MEMORY_LIMIT, PMAT_API_TOKEN, PMAT_DEBUG, PMAT_LOG_LEVEL and PMAT_CACHE_DIR — of which seven appear nowhere in the pmat source at all. PMAT_CACHE_DIR is the one that is real, but no --help declares it, so it is listed here as a source-level detail rather than a supported interface.

Exit codes

Measured, not documented by the tool. Earlier editions of this appendix listed ten codes (3 = analysis failure, 4 = quality gate failure, 5 = security violation, 20 = license error, …); pmat emits none of them.

A --fail-on-* style flag is what turns a finding into exit 1; without one, most analysis commands report and exit 0. Do not build CI on “pmat exited 0 therefore the code is clean” — check the flag list for the command you are running.

See also

• Chapter 5: The Analyze Command Suite — pmat analyze with worked examples
• Chapter 3.4: MCP Transports — the verified MCP surface
• Chapter 15: Complete MCP Tools Reference — the 19 MCP tools, read out of the server
• pmat <command> --help — always the authority; this appendix is generated from it