Skip to main content

Pipeline Diagnostics

squirex diagnose outputs a structured JSON report covering graph topology, linker trace, per-rule timing, and adversarial pattern detection. Use it to understand exactly what SquireX parsed and why rules fired (or didn't).

Commands​

# Full diagnostic report (JSON to stdout)
squirex diagnose -d ./force-app

# Inspect semantic graph topology
squirex diagnose -d ./force-app | jq .graph

# Per-rule timing and violation counts
squirex diagnose -d ./force-app | jq .rules

# Dropped / dangling cross-file edges
squirex diagnose -d ./force-app | jq .linker

# Dump scan-request.json for golden file testing
squirex diagnose -d ./force-app --dump-request

Report Structure​

{
  "graph": {
    "nodes": 48,
    "edges": 112,
    "nodeTypes": { "GenAiFunction": 12, "Apex": 18, "Flow": 6, ... }
  },
  "linker": {
    "resolved": 108,
    "dropped": 4,
    "dangling": [{ "from": "Submit_Case.genAiFunction", "to": "CaseHandler.cls", "reason": "not found in scan scope" }]
  },
  "rules": [
    { "id": "AGENTFORCE-1.1", "durationMs": 12, "violations": 1 },
    { "id": "AGENTFORCE-9.1", "durationMs": 45, "violations": 0 }
  ]
}

Common Uses​

GoalCommand
Why wasn't my Apex class linked?jq .linker.dangling — look for your file in reason
Which rules are slowest?`jq '.rules
How many nodes were discovered?jq .graph
Generate a reproducible scan payload--dump-request