Frequently Asked Questions
Browse common questions about how CXGRD works, what it analyzes, and which plan fits your team.
No. CXGRD complements testing and human code review by detecting the blast radius of a change — which files, functions, and dependencies are affected — before merge. Tests verify behavior; CXGRD identifies what's at risk from a change so you know where to focus testing and review attention.
CXGRD computes blast radius through deterministic dependency graph traversal — actual import and call relationships in your codebase — rather than an AI agent's interpretation of a diff. A dependency edge either exists or it doesn't; there's no model judgment or hallucination risk in the underlying analysis.
Yes. CXGRD's Team tier includes a dedicated `cxgrd check --ci` command and CI tokens for use in GitHub Actions or any CI pipeline, enforcing merge policies automatically before code ships.
Free covers core blast radius scanning for individual developers. Pro adds AI prompt enrichment and expanded scan limits. Team adds GitHub App integration, CI enforcement, merge policies, audit logs, and a team dashboard for organizations enforcing rules across multiple repos.
CXGRD builds a dependency graph of your codebase and evaluates each change against it, so it can trace impact beyond the literal lines changed — catching downstream effects a diff-only view would miss.
Core blast radius and dependency graph analysis run deterministically without sending code to an LLM. Optional AI prompt enrichment (Pro/Team tiers) uses Groq for that specific feature only.