Graphite vs Qodo

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Qodo
   Graphite~partialprobed5/10

   The standard llms.txt at the root domain returns 404, but probes show agent-friendly markdown docs (docs/get-started.md returns 200) that point to a Mintlify-hosted llms index, meaning an agent could be pointed at machine-readable docs via an indirect path rather than a canonical llms.txt. Missing for 10: a working llms.txt at the expected root URL, and clear first-party documentation advertising this llms/agent-doc endpoint as a supported entry point.

   • [probe] “PROBE llms.txt: HTTP 404 at https://graphite.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 200 at https://graphite.com/docs/get-started.md > ## Documentation Index > Fetch the complete documentation index at: ht…”

   proof ↗⚑ flag

   Qodo✓fullprobed8/10

   A live probe confirms Qodo publishes an llms.txt file at docs.qodo.ai/llms.txt returning HTTP 200 with a structured summary of the product, directly enabling an AI agent to be pointed at it for agent-oriented context. This is corroborated by extensive agent-facing documentation (Agentic Toolbox, MCP, CLI) showing Qodo actively targets AI agent consumption of its docs and capabilities. Missing for 10: independent (non-probe) confirmation that agents successfully consume/parse the llms.txt content in practice, and evidence of additional agent-oriented doc formats beyond the single llms.txt file.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.qodo.ai/llms.txt # Qodo Qodo is an AI code review and governance platform for engineering teams. I…”
   • [claimed-docs] “The Qodo Agentic Toolbox brings Qodo's code understanding, coding standards, and review capabilities into your existing coding agent.”
   • [claimed-docs] “Use MCP when you want to connect Qodo Agentic Toolbox managed skills to a remote or custom agent, workflow, or application.”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Qodo
   Graphite~partialprobed4/10

   Graphite's CLI is git-compatible and configurable (gt config, gt commands) and is scriptable in principle, and features like merge queue/automations suggest some CI-style automation, but there is no explicit documentation of headless/non-interactive CLI flags, CI pipeline examples, or a documented automation API for running Graphite entirely without a human in CI. missing for 10: explicit CI/headless mode docs, non-interactive flag examples, dedicated automation/CI integration guide.

   • [claimed-docs] “The Graphite CLI is fully compatible with git—just install it on an existing repository and begin using our suite of gt commands.”
   • [claimed-docs] “Run gt config to open an interactive menu which lets you configure your Graphite CLI.”
   • [claimed-docs] “The Graphite CLI is a tool to help you break up large engineering tasks into a series of small, incremental code changes directly from the c…”
   • [claimed-docs] “Unlimited AI Reviews * AI Review customizations * Automations * Merge Queue”
   • [probe] “official CLI documented at https://graphite.com/docs/install-the-cli”

   proof ↗⚑ flag

   Qodo✓fullprobed7/10

   Qodo's core PR-review bot runs automatically/headlessly on every pull request without manual invocation (qodo-docs-1, qodo-docs-26), and the Agentic Toolbox ships a CLI plus MCP server explicitly meant for automation/local or remote workflows (qodo-docs-5, qodo-docs-32, qodo-docs-33, qodo-probe-3/4), which can be scripted into CI. Missing for 10: an explicit first-party CI pipeline example (e.g., GitHub Actions/GitLab CI snippet running the CLI) and independent hands-on confirmation of headless CI usage.

   • [claimed-docs] “Once connected, Qodo automatically reviews every pull request in your li”
   • [claimed-docs] “Trigger a Qodo code review manually or automatically, and control when reviews run on a pull request.”
   • [claimed-docs] “Review changes before opening a pull request.”
   • [claimed-docs] “Use the Qodo Agentic Toolbox CLI when you want to use Qodo-managed skills locally.”
   • [claimed-docs] “Use MCP when you want to connect Qodo Agentic Toolbox managed skills to a remote or custom agent, workflow, or application.”
   • [probe] “official MCP server documented at https://docs.qodo.ai/agentic-toolbox/mcp”
   • [probe] “official CLI documented at https://docs.qodo.ai/agentic-toolbox/cli”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Graphite—none0/10

   Evidence shows Graphite ships its own 'GT MCP' server so that external AI agents can call Graphite's tools (graphite-docs-30, graphite-probe-4), which is the reverse direction of the story — Graphite acting as an MCP server, not as a client that lets users plug external MCP servers into Graphite's own agents/chat. There is no evidence that Graphite's Agents or Chat features can consume third-party MCP servers' tools.

   • [claimed-docs] “GT MCP allows AI agents to automatically create stacked PRs, breaking down large AI-generated changes into smaller, reviewable stacked pull …”
   • [probe] “official MCP server documented at https://graphite.com/docs/gt-mcp”
   • [claimed-docs] “Describe what you want built or fixed in plain language, and Agents will pull context from your repository, generate the changes, and open a…”
   • [claimed-docs] “Make direct code changes right from your PR page. Click Agent on the right side of the PR to get started.”

   proof ↗⚑ flag

   Qodo—none0/10

   All MCP-related evidence describes Qodo exposing its own Agentic Toolbox skills AS an MCP server for other agents (Claude Code, Codex, Kiro) to consume (qodo-docs-6, qodo-docs-33, qodo-probe-3), not Qodo itself acting as an MCP client that ingests external MCP servers' tools. No documentation shows a way to configure/plug third-party MCP servers into Qodo's own agent/CLI so it can use their tools.

   • [claimed-docs] “Use MCP when you want to connect Qodo Agentic Toolbox managed skills to a remote or custom agent, workflow, or application.”
   • [claimed-docs] “Retrieve and resolve review findings.”
   • [probe] “official MCP server documented at https://docs.qodo.ai/agentic-toolbox/mcp”
   • [claimed-docs] “Use Qodo with Claude to access Qodo Agentic Toolbox skills for understanding your codebase, reviewing changes, and resolving code review fin…”
   • [claimed-docs] “Use the Qodo plugin with the Codex agent to access Qodo Agentic Toolbox skills for understanding your codebase, reviewing changes, and resol…”
   • [claimed-docs] “Use Qodo with the Kiro agent to access Qodo Agentic Toolbox skills for understanding your codebase, reviewing changes, and resolving code re…”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Qodo
   Graphite✓fullprobed6/10

   Graphite documents an official MCP server at /docs/gt-mcp, directly matching the story of connecting an agent via an official MCP server, and Graphite is a dev-tool/platform (not itself an agent) so this axis applies. However, the evidence pack only confirms the page exists (probe) without excerpting its content, and there is no independent/hands-on corroboration of using it to connect an agent. Missing for 10: detailed docs content describing the MCP server's tools/capabilities, and community or hands-on confirmation of successful agent connection.

   • [probe] “official MCP server documented at https://graphite.com/docs/gt-mcp”
   • [claimed-docs] “Install the Graphite CLI using either Homebrew or npm”

   proof ↗⚑ flag

   Qodo✓fullprobed7/10

   Qodo documents an official MCP server (Agentic Toolbox MCP) explicitly for connecting Qodo's code-understanding, review, and rules skills to remote or custom agents, confirmed by both docs and a probe hit at the documented URL. missing for 10: independent/hands-on corroboration of MCP usage, detailed setup/auth documentation, and specifics on which skills/tools are exposed over MCP.

   • [claimed-docs] “Retrieve and resolve review findings.”
   • [claimed-docs] “Use MCP when you want to connect Qodo Agentic Toolbox managed skills to a remote or custom agent, workflow, or application.”
   • [probe] “official MCP server documented at https://docs.qodo.ai/agentic-toolbox/mcp”
   • [claimed-docs] “The Qodo Agentic Toolbox brings Qodo's code understanding, coding standards, and review capabilities into your existing coding agent.”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Graphite
   Graphite✓fullprobed9/10

   Graphite ships a well-documented official CLI (`gt`) installable via npm/Homebrew, fully git-compatible, with configuration (`gt config`) and a full command reference, and this is corroborated by extensive hands-on community use praising the CLI workflow. It also integrates with AI agent workflows via GT MCP for stacked PR creation, reinforcing agentic use. Missing for 10: no independent benchmark of CLI performance/reliability beyond anecdotal community reports (e.g., some bug reports on rebase/signing edge cases).

   • [claimed-docs] “Install the Graphite CLI using either Homebrew or npm”
   • [claimed-docs] “The Graphite CLI is fully compatible with git—just install it on an existing repository and begin using our suite of gt commands.”
   • [claimed-docs] “Run gt config to open an interactive menu which lets you configure your Graphite CLI.”
   • [claimed-docs] “The Graphite CLI is a tool to help you break up large engineering tasks into a series of small, incremental code changes directly from the c…”
   • [claimed-docs] “GT MCP allows AI agents to automatically create stacked PRs, breaking down large AI-generated changes into smaller, reviewable stacked pull …”
   • [probe] “official CLI documented at https://graphite.com/docs/install-the-cli”
   • [community] “Ive been using it since mote than a year and it has become part of my toolbelt. Especially the cli that allow to seemlessly rebase multiple …”
   • [community] “The main thing I found to be an improvement is that Graphite maintains all the stacking metadata in git refs. With the other tools, I did no…”

   proof ↗⚑ flag

   Qodo✓fullprobed8/10

   Qodo documents an official Agentic Toolbox CLI for local use (retrieving rules, reviewing changes before PR, resolving findings), and community evidence corroborates a real 'Qodo Command CLI' with agentic permission controls. Missing for 10: independent deep-dive review of CLI robustness/feature completeness and broader third-party adoption evidence beyond a single HN thread.

   • [claimed-docs] “Review changes before opening a pull request.”
   • [claimed-docs] “Retrieve the rules and standards that apply to a task.”
   • [claimed-docs] “Use the Qodo Agentic Toolbox CLI when you want to use Qodo-managed skills locally.”
   • [probe] “official CLI documented at https://docs.qodo.ai/agentic-toolbox/cli”
   • [community] “Slick. This applies to the new Qodo Command CLI, yes? I updated to the latest version last night. Enjoyed seeing the process permission togg…”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to Qodo
   Graphite~partialprobed5/10

   Graphite offers a documented CLI (gt commands) and an MCP server (gt-mcp) that let AI/agentic tooling drive the product, but there is no public REST/GraphQL/OpenAPI API — probes for openapi.json/swagger.json all 404. missing for 10: a documented general-purpose public API (REST/GraphQL) with endpoint reference, authentication scopes, and independent/hands-on corroboration of programmatic API usage beyond CLI/MCP.

   • [probe] “PROBE openapi: all candidate paths 404 (https://graphite.com/openapi.json, https://graphite.com/swagger.json, https://graphite.com/api/opena…”
   • [probe] “official MCP server documented at https://graphite.com/docs/gt-mcp”
   • [probe] “official CLI documented at https://graphite.com/docs/install-the-cli”
   • [claimed-docs] “Install the Graphite CLI using either Homebrew or npm”
   • [claimed-docs] “The Graphite CLI is fully compatible with git—just install it on an existing repository and begin using our suite of gt commands.”
   • [claimed-docs] “Run gt config to open an interactive menu which lets you configure your Graphite CLI.”

   proof ↗⚑ flag

   Qodo~partialprobed6/10

   Qodo documents an official MCP server and CLI (Agentic Toolbox) that let external agents retrieve findings, resolve reviews, and fetch rules programmatically, which is a documented interface for AI-native automation. However, a direct probe for a conventional public REST/OpenAPI API returned 404 on all candidate paths, so there is no traditional public API surface beyond the MCP/CLI toolbox. Missing for 10: a documented REST/OpenAPI-style public API, broader API reference docs, and independent confirmation of API robustness beyond first-party docs.

   • [claimed-docs] “Retrieve and resolve review findings.”
   • [claimed-docs] “Use MCP when you want to connect Qodo Agentic Toolbox managed skills to a remote or custom agent, workflow, or application.”
   • [claimed-docs] “Use the Qodo Agentic Toolbox CLI when you want to use Qodo-managed skills locally.”
   • [claimed-docs] “Retrieve the rules and standards that apply to a task.”
   • [probe] “official MCP server documented at https://docs.qodo.ai/agentic-toolbox/mcp”
   • [probe] “official CLI documented at https://docs.qodo.ai/agentic-toolbox/cli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.qodo.ai/openapi.json, https://docs.qodo.ai/swagger.json, https://docs.qodo.ai/api/opena…”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Graphite—none0/10

   No evidence describes scoped or least-privilege API credential/token issuance for agents; authentication is via GitHub App installation (org-wide) or MCP setup, with no mention of granular permission scoping for AI agent credentials. missing for 10: scoped/least-privilege credential issuance mechanism, token/permission granularity controls, any documentation of credential scoping for agents.

   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization.”
   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization”
   • [claimed-docs] “GT MCP allows AI agents to automatically create stacked PRs, breaking down large AI-generated changes into smaller, reviewable stacked pull …”

   proof ↗⚑ flag

   Qodo—none0/10

   Evidence shows admin control over who can access the Agentic Toolbox (qodo-docs-37) and a community mention of a process permission toggle (rwx) in the CLI (qodo-comm-3), but neither documents scoped or least-privilege API credentials/tokens issued specifically to an agent. No API key scoping, token minting, or credential-management docs appear in the pack.

   • [claimed-docs] “Workspace admins can control which users have access to the Qodo Agentic Toolbox. By default, the Agentic Toolbox is enabled for everyone in…”
   • [community] “Slick. This applies to the new Qodo Command CLI, yes? I updated to the latest version last night. Enjoyed seeing the process permission togg…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Graphite
   Graphite~partialprobed6/10

   Graphite ships an official CLI (gt) with npm/Homebrew install and documented config, plus a documented MCP server (gt-mcp), giving AI-native users official tooling to build against. However, there is no evidence of a general-purpose SDK (e.g., Python/JS client library) or public API/OpenAPI spec — probes for openapi.json all 404'd. missing for 10: official SDK/client libraries beyond the CLI, public API reference/OpenAPI spec, independent developer corroboration of building against these interfaces.

   • [claimed-docs] “Install the Graphite CLI using either Homebrew or npm”
   • [claimed-docs] “The Graphite CLI is fully compatible with git—just install it on an existing repository and begin using our suite of gt commands.”
   • [claimed-docs] “Run gt config to open an interactive menu which lets you configure your Graphite CLI.”
   • [probe] “official MCP server documented at https://graphite.com/docs/gt-mcp”
   • [probe] “official CLI documented at https://graphite.com/docs/install-the-cli”
   • [probe] “PROBE openapi: all candidate paths 404 (https://graphite.com/openapi.json, https://graphite.com/swagger.json, https://graphite.com/api/opena…”

   proof ↗⚑ flag

   Qodo—none0/10

   Qodo documents a CLI, an MCP server, and agent plugins (Claude, Codex, Kiro) for its Agentic Toolbox, but there is no evidence of an official SDK/client library for programmatic integration, and the OpenAPI/API-spec probe returned 404s across all candidate paths, indicating no public API surface to build an SDK against.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.qodo.ai/openapi.json, https://docs.qodo.ai/swagger.json, https://docs.qodo.ai/api/opena…”
   • [claimed-docs] “Use the Qodo Agentic Toolbox CLI when you want to use Qodo-managed skills locally.”
   • [claimed-docs] “Use MCP when you want to connect Qodo Agentic Toolbox managed skills to a remote or custom agent, workflow, or application.”
   • [probe] “official MCP server documented at https://docs.qodo.ai/agentic-toolbox/mcp”
   • [probe] “official CLI documented at https://docs.qodo.ai/agentic-toolbox/cli”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Graphite—none0/10

   The only webhook-related evidence describes Graphite *receiving* GitHub webhooks for CI/mergeability updates (graphite-docs-24), not Graphite exposing its own webhook subscription system for external/AI-native consumers to receive events. No documentation of an outbound webhook API, event types, or subscription mechanism is present.

   • [claimed-docs] “Receive GitHub webhooks for real-time updates on CI status, mergeability, and push events.”

   proof ↗⚑ flag

   Qodo—none0/10

   No evidence of a webhook subscription mechanism; Qodo offers MCP, CLI, and Git-provider integrations for reviews but nothing documented about outbound event webhooks for third-party subscription, and the openapi probe found no API spec either.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.qodo.ai/openapi.json, https://docs.qodo.ai/swagger.json, https://docs.qodo.ai/api/opena…”
   • [claimed-docs] “Connect Qodo to your Git provider to enable automated code reviews directly in your pull requests.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Graphite✓fullcommunity8/10

   Graphite ships AI Reviews that automatically analyze PRs and suggest fixes, a Graphite Chat that summarizes changes, suggests fixes, and explains code context, plus a dedicated 'Insights' feature to measure and optimize developer productivity — all directly generating AI insights/suggestions from repo data. Community feedback largely praises the stacking workflow with only general skepticism about AI additions, not a concrete failure of the insight/suggestion features themselves. Missing for 10: independent hands-on validation specifically of the Insights analytics dashboard and richer detail on what data-driven suggestions it surfaces beyond code review.

   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “Ask for suggested fixes and apply them in one click right from the review page.”
   • [claimed-docs] “InsightsMeasure and optimize your team's developer productivity.”
   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”
   • [claimed-docs] “Ask Graphite to explain what changed in a pull request, highlight potential issues, or provide context about specific code sections.”
   • [claimed-docs] “Get help understanding and implementing feedback from your teammates and reviewers.”
   • [community] “This is annoying, Graphite's core feature of stacked PRs is really good despite all the AI things they've added around their review UI. I do…”
   • [community] “i mentioned a few months ago that it was a shame where graphite was headed re: AI... this appears to be the final nail in the original produ…”

   proof ↗⚑ flag

   Qodo✓fullcommunity8/10

   Qodo generates AI-driven insights directly inside the product: PR summaries, ranked findings with rationale and fixes, risk/blast-radius classification, relevance links, and in-PR chat, all documented as core platform features (qodo-docs-2,3,8,22,23,24,27). This is corroborated by community mentions of using its review bot, though sentiment is mixed. Missing for 10: independent hands-on validation of insight accuracy/usefulness and some community reports of switching away from Qodo's bot temper full confidence.

   • [claimed-docs] “every finding states what needs attention, why it matters, and how to fix it, ranked by severity”
   • [claimed-docs] “Discuss or dismiss a finding, or let Qodo apply the fix directly.”
   • [claimed-docs] “Qodo makes this classification available as a native pull request tag (Azure DevOps) or label (GitHub, GitLab), so you can triage which pull…”
   • [claimed-docs] “Qodo reviews the full codebase, not just the diff, to generate a structured summary of the pull request (PR) that gives reviewers meaningf”
   • [claimed-docs] “Chat with Qodo to interact with Qodo directly inside pull requests.”
   • [claimed-docs] “The **Relevance** section highlights related pull requests wi”
   • [claimed-docs] “The review focuses on surfacing issues that matter, explaining why they matter, and helping developers resolve them efficiently, without ove…”
   • [community] “Was using their bot for code review for last 2 years but just dropped it for BugBot”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Graphite~partialclaimed6/10

   Graphite documents automation that runs without manual intervention: AI review agent automatically reviews all new PRs once enabled (graphite-docs-18, graphite-docs-19) and a stack-aware merge queue that lands PRs in the background (graphite-docs-10), plus Agents that autonomously generate PRs from a prompt (graphite-docs-12). This is real background automation, but scoped narrowly to PR review/merge events rather than a general-purpose 'set up any automation' framework with custom triggers/scheduling. Missing for 10: evidence of configurable triggers/schedules beyond PR events, and independent/hands-on confirmation that these automations reliably run unattended over time.

   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “Our stack-aware merge queue lands PRs in order and keeps branches green, helping you gain momentum.”
   • [claimed-docs] “Describe what you want built or fixed in plain language, and Agents will pull context from your repository, generate the changes, and open a…”

   proof ↗⚑ flag

   Qodo~partialclaimed6/10

   Qodo automatically reviews every PR in the background once connected (qodo-docs-1, qodo-docs-42, qodo-docs-26), and its governance features enforce standards across repos without manual intervention (qodo-docs-38), which qualifies as autonomous background automation for code review. However, this is scoped to PR review/governance rather than general-purpose autonomous agent workflows, and there's no evidence of scheduled/triggered custom automations beyond PR events. missing for 10: evidence of user-configurable autonomous triggers/schedules beyond PR events, independent hands-on confirmation that background automation runs reliably unattended, and broader autonomous task execution beyond code review/governance.

   • [claimed-docs] “Once connected, Qodo automatically reviews every pull request in your li”
   • [claimed-docs] “Trigger a Qodo code review manually or automatically, and control when reviews run on a pull request.”
   • [claimed-docs] “Qodo governance is built for engineering leaders who need consistent standards enforced across every repository, automatically, at scale, an…”
   • [claimed-docs] “Connect Qodo to your Git provider to enable automated code reviews directly in your pull requests.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Graphite
   Graphite✓fullcommunity8/10

   Graphite documents two built-in AI assistant surfaces: 'Graphite Agents' that take plain-language task descriptions, pull repo context, generate changes, and open a draft PR (graphite-docs-12, graphite-docs-22), and 'Graphite Chat' that can be asked to summarize PRs, suggest/apply fixes, and diagnose CI failures (graphite-docs-6/7/8/15/21) — directly matching task delegation to a built-in assistant. Community evidence shows real usage of Graphite generally but is skeptical/critical of the AI additions rather than confirming hands-on success (graphite-comm-10, graphite-comm-13), so independent corroboration of the delegation flow itself is thin. Missing for 10: independent/hands-on verification that Agents reliably complete delegated tasks end-to-end, and detail on failure modes.

   • [claimed-docs] “Describe what you want built or fixed in plain language, and Agents will pull context from your repository, generate the changes, and open a…”
   • [claimed-docs] “Make direct code changes right from your PR page. Click Agent on the right side of the PR to get started.”
   • [claimed-docs] ““Summarize the changes in this PR””
   • [claimed-docs] “Ask for suggested fixes and apply them in one click right from the review page.”
   • [claimed-docs] “Diagnose and resolve failing checks directly from your PR page with full context from your CI results.”
   • [claimed-docs] “Find related files, understand dependencies, and get context from other PRs without switching tabs.”
   • [claimed-docs] “Ask Graphite to explain what changed in a pull request, highlight potential issues, or provide context about specific code sections.”
   • [community] “This is annoying, Graphite's core feature of stacked PRs is really good despite all the AI things they've added around their review UI. I do…”
   • [community] “i mentioned a few months ago that it was a shame where graphite was headed re: AI... this appears to be the final nail in the original produ…”

   proof ↗⚑ flag

   Qodo✓fullcommunity7/10

   Qodo ships a built-in AI assistant that users can delegate review tasks to directly inside the product: chatting with Qodo in PRs, having it apply fixes, triggering reviews, and a Command CLI with agentic permission controls noted by a community user. This is real delegation of tasks to an embedded assistant, though the scope is centered on code review/fix workflows rather than broader open-ended task delegation. Missing for 10: independent hands-on evidence of task delegation quality/reliability, and evidence of delegating non-review tasks (e.g. feature building) to the built-in assistant.

   • [claimed-docs] “Discuss or dismiss a finding, or let Qodo apply the fix directly.”
   • [claimed-docs] “Chat with Qodo to interact with Qodo directly inside pull requests.”
   • [claimed-docs] “Trigger a Qodo code review manually or automatically, and control when reviews run on a pull request.”
   • [claimed-docs] “The review focuses on surfacing issues that matter, explaining why they matter, and helping developers resolve them efficiently, without ove…”
   • [community] “Slick. This applies to the new Qodo Command CLI, yes? I updated to the latest version last night. Enjoyed seeing the process permission togg…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Graphite
   Graphite✓fullclaimed7/10

   Graphite Chat lets users ask natural-language questions and request fixes ('Summarize the changes', 'Ask for suggested fixes and apply them in one click'), and Graphite Agents let users 'describe what you want built or fixed in plain language' to generate a draft PR — both are documented natural-language interaction surfaces layered on top of the core git/CLI workflow. Missing for 10: independent/hands-on corroboration that NL commands reliably work in practice (community evidence focuses on the CLI stacking workflow, not the NL chat/agent features) and clarity on how much of daily operation still requires explicit `gt` CLI commands rather than NL.

   • [claimed-docs] ““Summarize the changes in this PR””
   • [claimed-docs] “Ask for suggested fixes and apply them in one click right from the review page.”
   • [claimed-docs] “Diagnose and resolve failing checks directly from your PR page with full context from your CI results.”
   • [claimed-docs] “Describe what you want built or fixed in plain language, and Agents will pull context from your repository, generate the changes, and open a…”
   • [claimed-docs] “Ask Graphite to explain what changed in a pull request, highlight potential issues, or provide context about specific code sections.”
   • [claimed-docs] “Make direct code changes right from your PR page. Click Agent on the right side of the PR to get started.”
   • [claimed-docs] “With Graphite Chat, you can ask for context on code changes, get instant feedback, and make edits directly from the chat interface without l…”

   proof ↗⚑ flag

   Qodo~partialclaimed6/10

   Qodo supports conversational interaction via 'Chat with Qodo' in pull requests, letting users discuss, dismiss, or apply fixes to findings in natural language (qodo-docs-3, qodo-docs-23), and its Agentic Toolbox exposes skills to other NL-driven agents (Claude, Codex, Kiro) via CLI/MCP (qodo-docs-29–33). However, most core operation (triggering reviews, configuration, governance rules) is done via portal settings or config-as-code files rather than natural-language commands. Missing for 10: evidence of a general NL command interface for controlling reviews/settings outside chat, and independent hands-on confirmation of chat reliability.

   • [claimed-docs] “Discuss or dismiss a finding, or let Qodo apply the fix directly.”
   • [claimed-docs] “Chat with Qodo to interact with Qodo directly inside pull requests.”
   • [claimed-docs] “Use Qodo with Claude to access Qodo Agentic Toolbox skills for understanding your codebase, reviewing changes, and resolving code review fin…”
   • [claimed-docs] “Use the Qodo plugin with the Codex agent to access Qodo Agentic Toolbox skills for understanding your codebase, reviewing changes, and resol…”
   • [claimed-docs] “Use Qodo with the Kiro agent to access Qodo Agentic Toolbox skills for understanding your codebase, reviewing changes, and resolving code re…”
   • [claimed-docs] “Use the Qodo Agentic Toolbox CLI when you want to use Qodo-managed skills locally.”
   • [claimed-docs] “Use MCP when you want to connect Qodo Agentic Toolbox managed skills to a remote or custom agent, workflow, or application.”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Graphite—none0/10

   No evidence of an interactive API reference or runnable examples; OpenAPI/swagger probes returned 404 and no such documentation is mentioned anywhere in the pack.

   • [probe] “PROBE openapi: all candidate paths 404 (https://graphite.com/openapi.json, https://graphite.com/swagger.json, https://graphite.com/api/opena…”

   proof ↗⚑ flag

   Qodo—none0/10

   No evidence of an interactive API reference or runnable examples; the openapi probe explicitly returned 404 for all candidate paths, and no docs mention a sandbox/playground for API exploration.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.qodo.ai/openapi.json, https://docs.qodo.ai/swagger.json, https://docs.qodo.ai/api/opena…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Graphite—none0/10

   Probe explicitly found no OpenAPI/swagger spec at any standard path and no llms.txt, and no documentation references a machine-readable API spec download; only an MCP server and CLI are documented.

   • [probe] “PROBE openapi: all candidate paths 404 (https://graphite.com/openapi.json, https://graphite.com/swagger.json, https://graphite.com/api/opena…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://graphite.com/llms.txt”

   proof ↗⚑ flag

   Qodo—none0/10

   A direct probe for OpenAPI/Swagger specs at common paths returned 404s, and no documentation references a downloadable machine-readable API spec; only an llms.txt file and MCP/CLI tooling are documented, which are not equivalent to an API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.qodo.ai/openapi.json, https://docs.qodo.ai/swagger.json, https://docs.qodo.ai/api/opena…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.qodo.ai/llms.txt # Qodo Qodo is an AI code review and governance platform for engineering teams. I…”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Graphite—none0/10

   No evidence of any versioned API, API changelog, or documented deprecation policy — OpenAPI probes return 404 and no docs reference API versioning or deprecation practices.

   • [probe] “PROBE openapi: all candidate paths 404 (https://graphite.com/openapi.json, https://graphite.com/swagger.json, https://graphite.com/api/opena…”

   proof ↗⚑ flag

   Qodo—none0/10

   No evidence of a versioned API or a documented deprecation policy; the openapi.json probe found only 404s, and no changelog/versioning policy for APIs is mentioned. missing for 10: versioned public API reference, explicit API deprecation/versioning policy documentation, evidence of API version negotiation.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.qodo.ai/openapi.json, https://docs.qodo.ai/swagger.json, https://docs.qodo.ai/api/opena…”

   proof ↗⚑ flag

Ai authored

1. ai-native userThe reviewer holds the line on AI-generated PRs — it verifies agent-authored code at a volume no human team could review

   weight 2 · round to Qodo
   Graphite~partialcommunity6/10

   Graphite's AI reviews automatically scan every PR with no configuration, offer custom rules/comment exclusions, and GT MCP explicitly supports breaking large AI-agent-generated changes into reviewable stacked PRs — directly addressing reviewing agent-authored code. However, evidence is entirely first-party docs with no independent benchmarking of review accuracy/volume specifically for AI-generated code, and community commentary shows some skepticism about the direction of AI features (though not a concrete failure report). Missing for 10: independent/hands-on validation of review quality at scale on AI-authored PRs specifically, and any metrics on catch-rate or false-positive rate.

   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “AI reviews powered by Graphite Agent help your team build better software by automatically reviewing pull requests and catching bugs before …”
   • [claimed-docs] “GT MCP allows AI agents to automatically create stacked PRs, breaking down large AI-generated changes into smaller, reviewable stacked pull …”
   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [community] “i mentioned a few months ago that it was a shame where graphite was headed re: AI... this appears to be the final nail in the original produ…”

   proof ↗⚑ flag

   Qodo~partialcommunity7/10

   Qodo automatically reviews every PR, surfaces ranked findings with severity/rationale, supports blast-radius risk classification to triage high-risk changes, and offers governance/config-as-code to enforce standards at scale — all pointing at reviewing AI-authored code at volume. However, there's no explicit evidence or metrics about reviewing agent-authored PRs specifically at a volume beyond human capacity, nor independent/hands-on validation of throughput or accuracy claims; one community comment even shows a long-time user switching away to a competitor. Missing for 10: quantified throughput/scale benchmarks for agent-authored PRs, explicit agent-vs-human-authored PR handling, and independent corroboration of review quality at scale.

   • [claimed-docs] “Once connected, Qodo automatically reviews every pull request in your li”
   • [claimed-docs] “every finding states what needs attention, why it matters, and how to fix it, ranked by severity”
   • [claimed-docs] “Qodo makes this classification available as a native pull request tag (Azure DevOps) or label (GitHub, GitLab), so you can triage which pull…”
   • [claimed-docs] “Qodo automatically classifies the risk of a code change and can publish it as a native label in the pull request, helping teams triage which…”
   • [claimed-docs] “Qodo governance is built for engineering leaders who need consistent standards enforced across every repository, automatically, at scale, an…”
   • [claimed-docs] “The review focuses on surfacing issues that matter, explaining why they matter, and helping developers resolve them efficiently, without ove…”
   • [community] “Was using their bot for code review for last 2 years but just dropped it for BugBot”

   proof ↗⚑ flag

Checks

1. ai-native userI define custom agentic pre-merge checks in plain language — 'docs updated', 'tests cover new paths' — that run on every PR

   weight 2 · round drawn
   Graphite~partialclaimed5/10

   Graphite Agent supports 'Custom rules' where users define plain-language guidelines for the AI reviewer to follow on every PR (graphite-docs-5, graphite-docs-20/28), and AI reviews run automatically on all PRs with no configuration (graphite-docs-18/19). However, these are review comments/guidelines, not documented as blocking, pass/fail 'checks' that gate merge like a CI status (e.g., 'docs updated' or 'tests cover new paths' as enforced gates) — the merge queue and check-diagnosis features are separate from these custom rules. Missing for 10: explicit documentation of custom rules acting as blocking/required pre-merge gates rather than advisory review comments, and examples matching the exact 'docs updated'/'tests cover new paths' framing.

   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should **not** leave comments.”
   • [claimed-docs] “Unlimited AI Reviews * AI Review customizations * Automations * Merge Queue”

   proof ↗⚑ flag

   Qodo~partialclaimed5/10

   Qodo does support defining and enforcing custom engineering standards via a centralized rule system, config-as-code (.pr_agent.toml), and Rule Miner that generates rules from PR history, which are automatically applied on every PR review. However, the evidence never shows a documented feature for writing arbitrary plain-language pre-merge gates like 'docs updated' or 'tests cover new paths' that block/pass PRs as discrete agentic checks. Missing for 10: explicit examples of natural-language custom check definitions, evidence of pass/fail merge-gating behavior, and confirmation these rules run as discrete checks rather than general review guidance.

   • [claimed-docs] “Manage Qodo configuration as code using a .pr\_agent.toml file at the repository, project, group, or organization level.”
   • [claimed-docs] “Define and enforce engineering standards with a centralized rule system.”
   • [claimed-docs] “Generate rules from pull request history with Rule Miner”
   • [claimed-docs] “Manage Qodo configuration as code using a .pr_agent.toml file at the repository, project, group, or organization level.”

   proof ↗⚑ flag

Fixes

1. developerI turn a review finding into an applied fix — a committed patch or an agent-generated follow-up — without leaving the PR

   weight 3 · round drawn
   Graphite✓fullclaimed7/10

   Docs explicitly describe applying AI-suggested fixes in one click from the PR review page and making direct agent-driven code changes without leaving the PR (docs-7, docs-22), plus diagnosing/resolving failing checks in-PR (docs-8). This directly matches the story of turning a review finding into an applied fix in-place. Missing for 10: independent/hands-on corroboration of the one-click apply-fix and in-PR agent edit flow (community evidence only covers stacking, not this AI-fix feature), and no detail on how committed-patch fixes are verified/tested post-apply.

   • [claimed-docs] “Ask for suggested fixes and apply them in one click right from the review page.”
   • [claimed-docs] “Make direct code changes right from your PR page. Click Agent on the right side of the PR to get started.”
   • [claimed-docs] “Diagnose and resolve failing checks directly from your PR page with full context from your CI results.”
   • [claimed-docs] “Describe what you want built or fixed in plain language, and Agents will pull context from your repository, generate the changes, and open a…”

   proof ↗⚑ flag

   Qodo✓fullclaimed7/10

   Qodo's docs explicitly describe turning a review finding into an applied fix within the PR: 'Discuss or dismiss a finding, or let Qodo apply the fix directly' and 'Chat with Qodo... directly inside pull requests,' plus MCP/CLI/agent-plugin tools to 'retrieve and resolve review findings' for follow-up agent workflows (Claude, Codex, Kiro). This covers both the committed-patch and agent-generated-follow-up paths without leaving the PR context. Missing for 10: independent/hands-on confirmation that the 'apply fix directly' button reliably produces a working commit, and no community evidence specifically validating this exact workflow.

   • [claimed-docs] “Discuss or dismiss a finding, or let Qodo apply the fix directly.”
   • [claimed-docs] “Retrieve and resolve review findings.”
   • [claimed-docs] “Chat with Qodo to interact with Qodo directly inside pull requests.”
   • [claimed-docs] “Use Qodo with Claude to access Qodo Agentic Toolbox skills for understanding your codebase, reviewing changes, and resolving code review fin…”
   • [claimed-docs] “Use the Qodo plugin with the Codex agent to access Qodo Agentic Toolbox skills for understanding your codebase, reviewing changes, and resol…”
   • [claimed-docs] “Use Qodo with the Kiro agent to access Qodo Agentic Toolbox skills for understanding your codebase, reviewing changes, and resolving code re…”
   • [claimed-docs] “Use MCP when you want to connect Qodo Agentic Toolbox managed skills to a remote or custom agent, workflow, or application.”

   proof ↗⚑ flag

Handoff

1. ai-native userReview findings hand off cleanly to my coding agent — copyable fix prompts or direct integration with Claude Code, Cursor, or Codex

   weight 2 · round to Qodo
   Graphite~partialprobed5/10

   Graphite offers its own Agent that applies suggested fixes in one click and opens draft PRs from review feedback, plus a GT MCP server that lets external AI agents interact with Graphite to create stacked PRs — this provides a form of agent handoff. However, there is no explicit documentation of copyable fix prompts or named integrations with Claude Code, Cursor, or Codex; the flow relies on Graphite's own in-house Agent or generic MCP tooling rather than a documented direct connector to those specific coding agents. Missing for 10: explicit copyable fix-prompt format, named integration/setup docs for Claude Code/Cursor/Codex, and independent evidence such handoffs work in practice.

   • [claimed-docs] “Ask for suggested fixes and apply them in one click right from the review page.”
   • [claimed-docs] “Make direct code changes right from your PR page. Click Agent on the right side of the PR to get started.”
   • [claimed-docs] “GT MCP allows AI agents to automatically create stacked PRs, breaking down large AI-generated changes into smaller, reviewable stacked pull …”
   • [probe] “official MCP server documented at https://graphite.com/docs/gt-mcp”

   proof ↗⚑ flag

   Qodo✓fullprobed7/10

   Qodo's Agentic Toolbox explicitly ships review-finding resolution into coding agents via a Claude Code plugin, a Codex plugin, a CLI ('Retrieve and resolve review findings'), and an MCP server for connecting to 'a remote or custom agent, workflow, or application' (which would cover Cursor). This directly matches the hand-off-to-coding-agent story. Missing for 10: an explicit named Cursor plugin/integration, independent/hands-on confirmation that the hand-off works smoothly in practice, and details on the 'copyable fix prompt' UX itself.

   • [claimed-docs] “The Qodo Agentic Toolbox brings Qodo's code understanding, coding standards, and review capabilities into your existing coding agent.”
   • [claimed-docs] “Retrieve and resolve review findings.”
   • [claimed-docs] “Use Qodo with Claude to access Qodo Agentic Toolbox skills for understanding your codebase, reviewing changes, and resolving code review fin…”
   • [claimed-docs] “Use the Qodo plugin with the Codex agent to access Qodo Agentic Toolbox skills for understanding your codebase, reviewing changes, and resol…”
   • [claimed-docs] “Use the Qodo Agentic Toolbox CLI when you want to use Qodo-managed skills locally.”
   • [claimed-docs] “Use MCP when you want to connect Qodo Agentic Toolbox managed skills to a remote or custom agent, workflow, or application.”
   • [probe] “official MCP server documented at https://docs.qodo.ai/agentic-toolbox/mcp”
   • [probe] “official CLI documented at https://docs.qodo.ai/agentic-toolbox/cli”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Graphite
   Graphite~partialcommunity6/10

   Graphite's CLI and stacking model let users manipulate many branches/PRs at once (community confirms 'rebase multiple branches at the same time'), the merge queue lands multiple PRs in order, and cross-repo PR tracking/AI review runs across all PRs in a repo automatically. However, the AI/agent features (Graphite Agent, chat, fix suggestions) are documented as per-PR actions, not as a bulk/batch operation across many items simultaneously. Missing for 10: explicit bulk AI-agent operations (e.g., batch-generate or batch-fix across many PRs/repos in one command), and independent evidence of scale beyond git-stack rebasing.

   • [claimed-docs] “Our stack-aware merge queue lands PRs in order and keeps branches green, helping you gain momentum.”
   • [claimed-docs] “Stay up-to-date with PRs across many repos using custom filters and rules.”
   • [community] “Ive been using it since mote than a year and it has become part of my toolbelt. Especially the cli that allow to seemlessly rebase multiple …”
   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”

   proof ↗⚑ flag

   Qodo~partialclaimed5/10

   Qodo's docs describe automatic, organization-wide operations that touch many items at once — it reviews every PR in a connected list, applies org-level configuration to all repositories, and enforces governance/standards 'across every repository, automatically, at scale' — which is a form of bulk operation. However there's no explicit documentation of a user-triggered bulk action (e.g., select multiple PRs/findings and apply a fix or dismiss in one operation) or independent evidence of this working at scale in practice. Missing for 10: explicit bulk-action UI/API across arbitrary item sets, hands-on/independent verification of scale performance, and confirmation that fixes/findings can be batch-resolved rather than one PR at a time.

   • [claimed-docs] “Once connected, Qodo automatically reviews every pull request in your li”
   • [claimed-docs] “Organization level (default): Settings apply to all connected repositories. Repository level: Settings apply only to the selected repository…”
   • [claimed-docs] “Qodo governance is built for engineering leaders who need consistent standards enforced across every repository, automatically, at scale, an…”
   • [claimed-docs] “Generate rules from pull request history with Rule Miner”
   • [claimed-docs] “The recommended way to manage organization-wide and repository-level code review configuration, from the Configurations page in the Qodo por…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Qodo
   Graphite~partialclaimed5/10

   Graphite ships some rule/event-driven automation: AI review auto-triggers on new PRs with no configuration (docs-19, docs-18), custom rules constrain when the review agent comments (docs-5, docs-20, docs-28), and a named 'Automations' feature appears in pricing (docs-33) alongside webhook-driven CI/merge event handling (docs-24) and stack-aware merge queue automation (docs-10). However, there is no dedicated documentation describing a general-purpose rules engine where a user defines arbitrary event→action triggers beyond PR-review and merge behaviors. Missing for 10: dedicated docs for the 'Automations' feature explaining supported trigger events/actions, evidence of custom/arbitrary action definitions beyond review-comment suppression, and independent confirmation of automation reliability.

   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should **not** leave comments.”
   • [claimed-docs] “Unlimited AI Reviews * AI Review customizations * Automations * Merge Queue”
   • [claimed-docs] “Receive GitHub webhooks for real-time updates on CI status, mergeability, and push events.”
   • [claimed-docs] “Our stack-aware merge queue lands PRs in order and keeps branches green, helping you gain momentum.”

   proof ↗⚑ flag

   Qodo~partialclaimed6/10

   Qodo documents a rule system for coding standards (qodo-docs-12, qodo-docs-13 Rule Miner) and automatic triggering of reviews on PR events with configurable rules (qodo-docs-26), plus config-as-code and org-wide enforcement (qodo-docs-11, qodo-docs-38). However, the 'rules' are scoped to code review/standards enforcement rather than a general-purpose event→action automation engine (e.g., arbitrary triggers/actions beyond reviews), and there's no independent/hands-on evidence confirming custom rule-trigger behavior works as described. Missing for 10: evidence of broader event types/actions beyond PR review triggering, and independent corroboration of rule automation working reliably.

   • [claimed-docs] “Define and enforce engineering standards with a centralized rule system.”
   • [claimed-docs] “Generate rules from pull request history with Rule Miner”
   • [claimed-docs] “Trigger a Qodo code review manually or automatically, and control when reviews run on a pull request.”
   • [claimed-docs] “Qodo governance is built for engineering leaders who need consistent standards enforced across every repository, automatically, at scale, an…”
   • [claimed-docs] “Manage Qodo configuration as code using a .pr\_agent.toml file at the repository, project, group, or organization level.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Graphite—none0/10

   No evidence of any scheduling, cron-like, or recurring job/workflow capability; Graphite's automation is event-triggered (PR opened, review requested) via AI reviews, merge queue, and MCP-driven agent actions, not time-based recurring jobs. Missing for 10: any documentation of scheduled/recurring triggers, cron syntax, or periodic workflow execution.

   ⚑ flag

   Qodo—none0/10

   Qodo's docs describe reviews triggered by PR events (manually or automatically on pull request activity) but there is no evidence of a scheduler, cron-like recurring job configuration, or workflow automation that runs independent of Git events. missing for 10: scheduled/cron-based triggers, recurring workflow definitions, any UI or config for time-based automation.

   • [claimed-docs] “Trigger a Qodo code review manually or automatically, and control when reviews run on a pull request.”
   • [claimed-docs] “Connect Qodo to your Git provider to enable automated code reviews directly in your pull requests.”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Graphite
   Graphite~partialclaimed5/10

   Graphite's AI Agents and GT MCP generate changes as ordinary PR/stack commits (graphite-docs-12, graphite-docs-22, graphite-docs-30), which are then subject to Graphite's git-based versioning, AI/human review (graphite-docs-4, graphite-docs-27) and standard git rollback (amend/rebase, graphite-docs-36). However there is no dedicated feature for versioning, auditing, or rolling back the automations/agent configurations themselves (e.g. custom review rules, agent settings) — the 'Automations' pricing bullet (graphite-docs-33) is undetailed. Missing for 10: explicit docs on automation config version history, audit trail of rule changes, and a rollback mechanism for automation behavior itself.

   • [claimed-docs] “Describe what you want built or fixed in plain language, and Agents will pull context from your repository, generate the changes, and open a…”
   • [claimed-docs] “Make direct code changes right from your PR page. Click Agent on the right side of the PR to get started.”
   • [claimed-docs] “GT MCP allows AI agents to automatically create stacked PRs, breaking down large AI-generated changes into smaller, reviewable stacked pull …”
   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “AI reviews powered by Graphite Agent help your team build better software by automatically reviewing pull requests and catching bugs before …”
   • [claimed-docs] “Amend staged changes to the relevant commits in the current stack.”
   • [claimed-docs] “Unlimited AI Reviews * AI Review customizations * Automations * Merge Queue”

   proof ↗⚑ flag

   Qodo~partialclaimed4/10

   Qodo supports managing its review configuration "as code" via a .pr_agent.toml file at repo/org level, which implies git-based versioning and rollback of automation settings, and offers org vs repo-level overrides in the portal. However, there is no explicit documented version-history UI or one-click rollback feature for automations/configurations themselves. Missing for 10: dedicated version history/audit trail for config changes, explicit rollback mechanism beyond inferred git revert, and any review workflow specifically for undoing automation changes.

   • [claimed-docs] “Manage Qodo configuration as code using a .pr\_agent.toml file at the repository, project, group, or organization level.”
   • [claimed-docs] “Manage Qodo configuration as code using a .pr_agent.toml file at the repository, project, group, or organization level.”
   • [claimed-docs] “Organization level (default): Settings apply to all connected repositories. Repository level: Settings apply only to the selected repository…”
   • [claimed-docs] “The recommended way to manage organization-wide and repository-level code review configuration, from the Configurations page in the Qodo por…”
   • [claimed-docs] “Choose a ready-made preset, Minimal, Standard, Comprehensive, or Custom, instead of setting each Display option individually.”

   proof ↗⚑ flag

Context

1. engineering leadThe reviewer understands changes that span multiple repositories or a large monorepo and reviews them coherently

   weight 2 · round to Qodo
   Graphite~partialclaimed4/10

   Graphite offers cross-repo PR tracking with custom filters (docs-11) and a codebase-aware AI reviewer that pulls related files/dependencies/context from other PRs (docs-15, docs-16), which helps a lead follow changes broadly, but there is no evidence of explicit monorepo-scale review tooling, cross-repo stack visualization, or dependency mapping across repositories in a single coherent review flow. Missing for 10: monorepo-specific review features, cross-repo diff/stack visualization, and independent evidence that reviewers actually use it to understand large or multi-repo spans coherently.

   • [claimed-docs] “Stay up-to-date with PRs across many repos using custom filters and rules.”
   • [claimed-docs] “Find related files, understand dependencies, and get context from other PRs without switching tabs.”
   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”

   proof ↗⚑ flag

   Qodo~partialclaimed7/10

   Qodo's docs describe cross-repo/system-level features relevant to an engineering lead reviewing multi-repo or monorepo changes: a 'Software Map' and code-governance view that shows 'how repositories, services and teams are connected to understand how code changes impact the full system' (qodo-docs-14, qodo-docs-34), org-wide risk/blast-radius classification and PR labeling for triage (qodo-docs-8, qodo-docs-25), and org-level configuration applied across all connected repositories (qodo-docs-10). Reviews also use full-codebase context rather than just the diff (qodo-docs-22). Missing for 10: explicit monorepo-specific handling/performance claims, independent or hands-on validation of cross-repo coherence, and concrete examples of reviewing a single change spanning multiple repos.

   • [claimed-docs] “Learn how repositories, services and teams are connected to understand how code changes impact the full system.”
   • [claimed-docs] “Software Map gives you a live view”
   • [claimed-docs] “Qodo makes this classification available as a native pull request tag (Azure DevOps) or label (GitHub, GitLab), so you can triage which pull…”
   • [claimed-docs] “Qodo automatically classifies the risk of a code change and can publish it as a native label in the pull request, helping teams triage which…”
   • [claimed-docs] “Organization level (default): Settings apply to all connected repositories. Repository level: Settings apply only to the selected repository…”
   • [claimed-docs] “Qodo reviews the full codebase, not just the diff, to generate a structured summary of the pull request (PR) that gives reviewers meaningf”
   • [claimed-docs] “Qodo governance is built for engineering leaders who need consistent standards enforced across every repository, automatically, at scale, an…”

   proof ↗⚑ flag

2. developerReview comments reflect the whole repository — call sites, related modules, existing conventions — not just the changed hunks

   weight 3 · round to Qodo
   Graphite✓fullclaimed7/10

   Graphite's AI review docs explicitly claim a 'codebase-aware AI code review agent' (docs-16) and Graphite Chat can 'find related files, understand dependencies, and get context from other PRs without switching tabs' (docs-15) plus explain code sections and highlight issues with repo context (docs-21), directly supporting whole-repo-aware review beyond the diff. Missing for 10: independent/hands-on validation that reviews actually surface call sites and existing conventions (not just vendor claims), and no explicit mention of 'existing conventions' detection.

   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”
   • [claimed-docs] “Find related files, understand dependencies, and get context from other PRs without switching tabs.”
   • [claimed-docs] “Ask Graphite to explain what changed in a pull request, highlight potential issues, or provide context about specific code sections.”
   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”

   proof ↗⚑ flag

   Qodo✓fullclaimed8/10

   Qodo explicitly documents that it 'reviews the full codebase, not just the diff' to generate context-aware summaries, surfaces related pull requests via a Relevance section, maps repository/service/team connections to understand system-wide impact, and enforces org-wide coding conventions via a centralized rule system — directly supporting repo-wide, cross-module review context beyond changed hunks. Missing for 10: independent/hands-on verification that comments concretely reference call sites and existing conventions in practice, rather than only documented capability claims.

   • [claimed-docs] “Qodo reviews the full codebase, not just the diff, to generate a structured summary of the pull request (PR) that gives reviewers meaningf”
   • [claimed-docs] “The **Relevance** section highlights related pull requests wi”
   • [claimed-docs] “Learn how repositories, services and teams are connected to understand how code changes impact the full system.”
   • [claimed-docs] “Define and enforce engineering standards with a centralized rule system.”
   • [claimed-docs] “Qodo governance is built for engineering leaders who need consistent standards enforced across every repository, automatically, at scale, an…”
   • [claimed-docs] “The review focuses on surfacing issues that matter, explaining why they matter, and helping developers resolve them efficiently, without ove…”

   proof ↗⚑ flag

Memory

1. ai-native userThe reviewer builds a persistent memory of my team's conventions and past review decisions and applies it to future PRs

   weight 2 · round to Qodo
   Graphite~partialclaimed4/10

   Graphite lets teams define persistent 'custom rules' and comment exclusions that the AI reviewer follows across future PRs, which is a form of encoded team convention (graphite-docs-5, graphite-docs-20), and AI reviews run automatically without reconfiguration per PR (graphite-docs-19). However, there is no evidence this memory is built from or updates based on past review decisions/outcomes—rules must be manually authored, not learned—so the 'past review decisions' half of the story is unsupported. missing for 10: evidence of automatic learning from historical review decisions, evidence of memory evolving over time without manual rule-writing, independent confirmation that custom rules persist and are applied consistently across many PRs.

   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”

   proof ↗⚑ flag

   Qodo✓fullclaimed7/10

   Qodo documents a persistent memory system for conventions via a 'centralized rule system' and 'Rule Miner' that generates rules from PR history (qodo-docs-12, qodo-docs-13), plus a full history of past findings/decisions/codebase health (qodo-docs-15) and governance enforced automatically across repos (qodo-docs-38), with rules retrievable per task (qodo-docs-7) and configurable as code across org/repo levels (qodo-docs-11/36). This directly matches building and applying institutional memory to future PRs. Missing for 10: independent/hands-on validation of Rule Miner's accuracy or how conventions evolve over time, and no community evidence corroborating this specific memory feature.

   • [claimed-docs] “Define and enforce engineering standards with a centralized rule system.”
   • [claimed-docs] “Generate rules from pull request history with Rule Miner”
   • [claimed-docs] “See a complete history of findings, decisions, and codebase health.”
   • [claimed-docs] “Qodo governance is built for engineering leaders who need consistent standards enforced across every repository, automatically, at scale, an…”
   • [claimed-docs] “Retrieve the rules and standards that apply to a task.”
   • [claimed-docs] “Manage Qodo configuration as code using a .pr\_agent.toml file at the repository, project, group, or organization level.”
   • [claimed-docs] “Manage Qodo configuration as code using a .pr_agent.toml file at the repository, project, group, or organization level.”

   proof ↗⚑ flag

Chat

1. developerI reply to the reviewer in the PR thread to ask questions, get explanations, or issue commands — and it answers in context

   weight 2 · round drawn
   Graphite✓fullclaimed7/10

   Graphite Chat is documented to let developers ask questions, get explanations of changes, request suggested fixes, get help implementing reviewer feedback, and diagnose CI issues directly from the PR page in context — matching the interaction story closely (graphite-docs-6,7,8,15,21,29,35). Missing for 10: independent/hands-on user testimony specifically validating Graphite Chat's conversational quality (community evidence covers CLI/stacking, not chat interactions), and no detail on command-issuing reliability via replies.

   • [claimed-docs] ““Summarize the changes in this PR””
   • [claimed-docs] “Ask for suggested fixes and apply them in one click right from the review page.”
   • [claimed-docs] “Diagnose and resolve failing checks directly from your PR page with full context from your CI results.”
   • [claimed-docs] “Find related files, understand dependencies, and get context from other PRs without switching tabs.”
   • [claimed-docs] “Ask Graphite to explain what changed in a pull request, highlight potential issues, or provide context about specific code sections.”
   • [claimed-docs] “With Graphite Chat, you can ask for context on code changes, get instant feedback, and make edits directly from the chat interface without l…”
   • [claimed-docs] “Get help understanding and implementing feedback from your teammates and reviewers.”

   proof ↗⚑ flag

   Qodo✓fullclaimed7/10

   Qodo docs explicitly describe an in-PR chat feature ('Chat with Qodo to interact with Qodo directly inside pull requests') plus the ability to discuss or dismiss findings within the thread, matching the story of replying to the reviewer for questions/commands with contextual answers. Missing for 10: independent/hands-on verification of chat quality and context-awareness, and no detail on the range of commands supported beyond discuss/dismiss/apply-fix.

   • [claimed-docs] “Chat with Qodo to interact with Qodo directly inside pull requests.”
   • [claimed-docs] “Discuss or dismiss a finding, or let Qodo apply the fix directly.”
   • [claimed-docs] “every finding states what needs attention, why it matters, and how to fix it, ranked by severity”

   proof ↗⚑ flag

Control

1. developerI control when reviews run — skip drafts, trigger on demand, filter by branch or label — so the bot shows up only when wanted

   weight 1 · round to Qodo
   Graphite~partialclaimed4/10

   Graphite lets teams turn AI review on per selected repository and use custom rules/comment exclusions to shape what the Agent flags (graphite-docs-19, graphite-docs-5, graphite-docs-20), giving some control over when/where the bot comments. However there is no documented ability to skip draft PRs, trigger a review on demand, or filter specifically by branch or label as the story requires. Missing for 10: draft-PR skip toggle, on-demand/manual trigger command, and branch/label-based filtering rules.

   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should **not** leave comments.”

   proof ↗⚑ flag

   Qodo~partialclaimed6/10

   Qodo docs explicitly state you can 'trigger a Qodo code review manually or automatically, and control when reviews run on a pull request' (qodo-docs-26), and configuration can be set at org/repo level or via a .pr_agent.toml config-as-code file (qodo-docs-10, qodo-docs-11), which implies fine-grained trigger control. However, the pack lacks explicit documentation of skipping draft PRs or filtering triggers by branch/label — the only label-related evidence is about risk classification tags for triage (qodo-docs-8, qodo-docs-25), not review-trigger filtering. Missing for 10: explicit doc/example of draft-PR skip, branch-based trigger rules, and label-based trigger filters.

   • [claimed-docs] “Trigger a Qodo code review manually or automatically, and control when reviews run on a pull request.”
   • [claimed-docs] “Organization level (default): Settings apply to all connected repositories. Repository level: Settings apply only to the selected repository…”
   • [claimed-docs] “Manage Qodo configuration as code using a .pr\_agent.toml file at the repository, project, group, or organization level.”
   • [claimed-docs] “Qodo makes this classification available as a native pull request tag (Azure DevOps) or label (GitHub, GitLab), so you can triage which pull…”
   • [claimed-docs] “Qodo automatically classifies the risk of a code change and can publish it as a native label in the pull request, helping teams triage which…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   Graphite~partialprobed4/10

   Graphite ships a git-compatible CLI (`gt` commands) covering the core stacking workflow and an MCP server that lets AI agents create stacked PRs programmatically, but there is no documented public REST/GraphQL API (openapi probe returned 404 on all candidate paths) covering UI-only features like AI review customization, Insights, merge queue configuration, or Graphite Chat — these appear web/GUI-only. missing for 10: a documented general-purpose API or OpenAPI spec exposing AI reviews, custom rules, insights, and merge queue equivalently to the UI; evidence that MCP/CLI cover the full breadth of UI functionality rather than just stacking.

   • [claimed-docs] “The Graphite CLI is fully compatible with git—just install it on an existing repository and begin using our suite of gt commands.”
   • [claimed-docs] “The Graphite CLI is a tool to help you break up large engineering tasks into a series of small, incremental code changes directly from the c…”
   • [claimed-docs] “GT MCP allows AI agents to automatically create stacked PRs, breaking down large AI-generated changes into smaller, reviewable stacked pull …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://graphite.com/openapi.json, https://graphite.com/swagger.json, https://graphite.com/api/opena…”
   • [probe] “official MCP server documented at https://graphite.com/docs/gt-mcp”
   • [probe] “official CLI documented at https://graphite.com/docs/install-the-cli”
   • [claimed-docs] “InsightsMeasure and optimize your team's developer productivity.”
   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”

   proof ↗⚑ flag

   Qodo~partialprobed4/10

   Qodo exposes a CLI and MCP server (Agentic Toolbox) that let agents review changes, retrieve findings, and fetch rules/standards, and configuration can be managed as code via .pr_agent.toml — some UI functions are scriptable. However there is no documented public REST/OpenAPI API (probe found openapi endpoints 404), and most UI-only features (portal configuration, governance dashboards, risk/blast-radius labels, PR chat, relevance, software map) have no evidenced programmatic equivalent for full parity. Missing for 10: a documented public API/OpenAPI spec, and API-equivalents for governance, risk classification, dashboards, and chat features shown only in the UI docs.

   • [claimed-docs] “Use the Qodo Agentic Toolbox CLI when you want to use Qodo-managed skills locally.”
   • [claimed-docs] “Use MCP when you want to connect Qodo Agentic Toolbox managed skills to a remote or custom agent, workflow, or application.”
   • [claimed-docs] “Retrieve and resolve review findings.”
   • [claimed-docs] “Retrieve the rules and standards that apply to a task.”
   • [claimed-docs] “Manage Qodo configuration as code using a .pr\_agent.toml file at the repository, project, group, or organization level.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.qodo.ai/openapi.json, https://docs.qodo.ai/swagger.json, https://docs.qodo.ai/api/opena…”
   • [probe] “official MCP server documented at https://docs.qodo.ai/agentic-toolbox/mcp”
   • [probe] “official CLI documented at https://docs.qodo.ai/agentic-toolbox/cli”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Graphite
   Graphite~partialcommunity4/10

   Graphite stores stacking metadata directly in git refs and its CLI is fully git-compatible, meaning core stack/branch data is inherently portable and not locked in a proprietary format (graphite-docs-3, graphite-comm-6), and community members have in fact migrated away to alternatives like git-spice/jujutsu without apparent data-loss complaints (graphite-comm-13). However, there is no explicit documented export feature for other Graphite-held data (AI review comments, insights/analytics, custom rules configs) in open formats. Missing for 10: a documented data-export tool/API for non-git data (reviews, insights, settings), explicit open-format guarantees, and hands-on confirmation of a full account data export.

   • [claimed-docs] “The Graphite CLI is fully compatible with git—just install it on an existing repository and begin using our suite of gt commands.”
   • [community] “The main thing I found to be an improvement is that Graphite maintains all the stacking metadata in git refs. With the other tools, I did no…”
   • [community] “i mentioned a few months ago that it was a shame where graphite was headed re: AI... this appears to be the final nail in the original produ…”

   proof ↗⚑ flag

   Qodo—none0/10

   No evidence of any data export feature, open-format export, or account/data portability mechanism; the only related item mentions strict data retention, not export, and there's no indication users can extract their review history, findings, or configuration data in a portable format. Missing for 10: any documented export/download feature, open format support, or data portability guarantee.

   • [claimed-docs] “Pricing FAQ: "Do you train AI models on my code? No. Qodo does not train models on your code. Your code is used only to generate reviews for…”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Graphite—none0/10

   No evidence indicates Graphite's source code is published under an open license; Graphite is a commercial SaaS/CLI product with docs, pricing, and GitHub App integration, but nothing about an open-source repository or license.

   ⚑ flag

   Qodo—none0/10

   No evidence Qodo's source code is available under an open license; Qodo is presented as a proprietary SaaS/on-prem product with no mention of open-sourcing its codebase.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Qodo
   Graphite—none0/10

   Graphite is a cloud SaaS product (CLI + hosted review/merge queue service) with no evidence of a self-hostable server/core; docs describe hosted authentication via GitHub App, cloud-based AI review, and pricing tiers, none of which mention on-prem or self-hosted deployment options.

   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization.”
   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization”
   • [claimed-docs] “Unlimited AI Reviews * AI Review customizations * Automations * Merge Queue”
   • [probe] “PROBE openapi: all candidate paths 404 (https://graphite.com/openapi.json, https://graphite.com/swagger.json, https://graphite.com/api/opena…”

   proof ↗⚑ flag

   Qodo✓fullclaimed7/10

   Qodo explicitly documents on-prem/self-managed deployment ('Deploy Qodo entirely within your own infrastructure', a dedicated on-prem deployment guide, and a deployment-model support table listing single-tenant, on-premises, and air-gapped options), directly satisfying the self-hosting story. Missing for 10: independent/hands-on confirmation that self-hosted deployments work as documented, and more detail on infrastructure requirements/limitations of the self-hosted mode.

   • [claimed-docs] “Deploy Qodo entirely within your own infrastructure.”
   • [claimed-docs] “This guide covers deploying Qodo in a self-managed infrastructure environment.”
   • [claimed-docs] “A reference table of supported deployment models for each Git provider, including multi-tenant, single-tenant, on-premises, and air-gapped o…”

   proof ↗⚑ flag

Platforms

1. developerThe reviewer installs as a GitHub/GitLab app and posts reviews as native inline comments on my pull requests within minutes

   weight 3 · round to Qodo
   Graphite~partialcommunity6/10

   Graphite documents GitHub App installation, automatic AI reviews on all new PRs with no configuration needed and quick 'few clicks' setup (graphite-docs-9, graphite-docs-18, graphite-docs-19), and comment exclusion rules imply it posts comments directly on PRs. However, there is no GitLab app support — community evidence explicitly notes Graphite lacks GitLab integration (graphite-comm-4) — and no explicit confirmation that comments are rendered as native inline PR comments or evidence of real-world review latency. Missing for 10: GitLab app support, explicit inline-comment rendering confirmation, independent verification of 'within minutes' turnaround.

   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization.”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [community] “I've followed Graphite for a while, and I just wish they supported GitLab. I know why they don't, but my current employer uses it and I've g…”

   proof ↗⚑ flag

   Qodo✓fullclaimed7/10

   Docs describe connecting Qodo to GitHub/GitLab via a guided setup wizard, automatic reviews on every PR, findings surfaced with severity that can be discussed/dismissed, chat inside PRs, and native labels/tags posted directly on the PR — consistent with an app-based inline review flow. Missing for 10: explicit wording confirming comments are 'inline' code comments (vs. summary/PR-level), an explicit time-to-first-review claim ('minutes'), and independent/hands-on confirmation beyond vendor docs.

   • [claimed-docs] “Connect Qodo to your Git provider to enable automated code reviews directly in your pull requests.”
   • [claimed-docs] “Once connected, Qodo automatically reviews every pull request in your li”
   • [claimed-docs] “After signing in for the first time, a setup wizard guides you through connecting Qodo to your development environment.”
   • [claimed-docs] “every finding states what needs attention, why it matters, and how to fix it, ranked by severity”
   • [claimed-docs] “Discuss or dismiss a finding, or let Qodo apply the fix directly.”
   • [claimed-docs] “Chat with Qodo to interact with Qodo directly inside pull requests.”
   • [claimed-docs] “Qodo automatically classifies the risk of a code change and can publish it as a native label in the pull request, helping teams triage which…”
   • [claimed-docs] “Trigger a Qodo code review manually or automatically, and control when reviews run on a pull request.”

   proof ↗⚑ flag

Suggestions

1. developerReview comments include committable suggested diffs I can apply with one click

   weight 3 · round drawn
   Graphite✓fullclaimed7/10

   Graphite's docs explicitly describe AI review suggestions with one-click apply ('Ask for suggested fixes and apply them in one click right from the review page') and AI reviews that 'suggest fixes instantly,' matching the story's core capability. Missing for 10: independent/hands-on confirmation that the applied fix is an actual committable diff (vs. just a chat suggestion) and no community citation validating the one-click apply UX in practice.

   • [claimed-docs] “Ask for suggested fixes and apply them in one click right from the review page.”
   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”

   proof ↗⚑ flag

   Qodo✓fullclaimed7/10

   Qodo's docs explicitly state that for each review finding you can 'discuss or dismiss a finding, or let Qodo apply the fix directly,' and findings include how-to-fix guidance, indicating one-click applicable suggested fixes within PR reviews (qodo-docs-2, qodo-docs-3). Missing for 10: explicit documentation of the diff/commit mechanics (e.g., 'commit suggestion' button semantics) and independent/hands-on confirmation from users that the apply-fix flow works as a one-click committable diff.

   • [claimed-docs] “every finding states what needs attention, why it matters, and how to fix it, ranked by severity”
   • [claimed-docs] “Discuss or dismiss a finding, or let Qodo apply the fix directly.”
   • [claimed-docs] “The review focuses on surfacing issues that matter, explaining why they matter, and helping developers resolve them efficiently, without ove…”

   proof ↗⚑ flag

Summaries

1. developerEvery PR gets an auto-generated summary and change walkthrough so human reviewers orient fast

   weight 2 · round to Qodo
   Graphite~partialclaimed6/10

   Graphite auto-runs AI reviews on every PR with no configuration needed (graphite-docs-4, graphite-docs-18, graphite-docs-19) and Graphite Chat can generate a PR summary/walkthrough on request ('Summarize the changes in this PR', 'explain what changed... highlight potential issues' — graphite-docs-6, graphite-docs-21, graphite-docs-15). However the summary/walkthrough capability appears to be a chat-driven, on-demand feature rather than an automatically-posted summary comment on every PR, and no evidence shows a structured 'walkthrough' artifact attached automatically like some competitors. Missing for 10: evidence of an automatically-posted summary/walkthrough comment on every PR (not just on-demand chat), and independent/hands-on confirmation of this specific behavior.

   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] ““Summarize the changes in this PR””
   • [claimed-docs] “Ask Graphite to explain what changed in a pull request, highlight potential issues, or provide context about specific code sections.”
   • [claimed-docs] “Find related files, understand dependencies, and get context from other PRs without switching tabs.”
   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”

   proof ↗⚑ flag

   Qodo✓fullclaimed9/10

   Qodo docs explicitly describe generating a structured PR summary from the full codebase (not just diff) to orient reviewers, plus a Relevance section highlighting related PRs and chat-with-Qodo-in-PR for further orientation, all triggered automatically on every PR. Missing for 10: independent/hands-on community confirmation specifically of the summary/walkthrough feature (community evidence covers other aspects like CLI and pricing, not this specific feature).

   • [claimed-docs] “Qodo reviews the full codebase, not just the diff, to generate a structured summary of the pull request (PR) that gives reviewers meaningf”
   • [claimed-docs] “The **Relevance** section highlights related pull requests wi”
   • [claimed-docs] “Chat with Qodo to interact with Qodo directly inside pull requests.”
   • [claimed-docs] “Once connected, Qodo automatically reviews every pull request in your li”
   • [claimed-docs] “Trigger a Qodo code review manually or automatically, and control when reviews run on a pull request.”

   proof ↗⚑ flag

Updates

1. developerPushing new commits triggers an incremental re-review that tracks what was fixed instead of repeating old comments

   weight 2 · round to Qodo
   Graphite—none0/10

   Docs confirm Graphite Agent automatically reviews all new pull requests and re-reviews on updates, but no evidence describes tracking which prior comments were resolved versus re-flagging them, or any incremental diff-aware re-review logic distinguishing fixed vs. unfixed issues.

   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “AI reviews powered by Graphite Agent help your team build better software by automatically reviewing pull requests and catching bugs before …”

   proof ↗⚑ flag

   Qodo~partialclaimed4/10

   Docs confirm reviews can be triggered automatically per push and controlled per PR (qodo-docs-26), and findings can be discussed/dismissed or auto-fixed (qodo-docs-3), implying some tracking of resolved issues, but there is no explicit documentation describing incremental re-review logic that specifically avoids repeating previously raised comments across new commits. missing for 10: explicit doc/example showing re-review skips already-addressed findings and only reports new/changed issues, independent confirmation of this behavior.

   • [claimed-docs] “Trigger a Qodo code review manually or automatically, and control when reviews run on a pull request.”
   • [claimed-docs] “Discuss or dismiss a finding, or let Qodo apply the fix directly.”
   • [claimed-docs] “The review focuses on surfacing issues that matter, explaining why they matter, and helping developers resolve them efficiently, without ove…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Qodo
   Graphite—none0/10

   No evidence of data residency/region selection controls; docs cover AI opt-in/no-training privacy but never mention where data is stored or region choice.

   ⚑ flag

   Qodo~partialclaimed5/10

   Qodo documents multiple deployment models—multi-tenant, single-tenant, on-premises, and air-gapped (qodo-docs-40, qodo-docs-39, qodo-docs-16)—which lets customers effectively control where their code/data resides by self-hosting infrastructure. However, there is no explicit 'choose a region' selector or data-residency policy for the standard SaaS offering, and qodo-supp-1 only addresses training/retention, not location. Missing for 10: explicit named regions/data centers for the hosted SaaS tier, and any documentation of a customer-facing region selection UI or policy.

   • [claimed-docs] “Deploy Qodo entirely within your own infrastructure.”
   • [claimed-docs] “This guide covers deploying Qodo in a self-managed infrastructure environment.”
   • [claimed-docs] “A reference table of supported deployment models for each Git provider, including multi-tenant, single-tenant, on-premises, and air-gapped o…”
   • [claimed-docs] “Pricing FAQ: "Do you train AI models on my code? No. Qodo does not train models on your code. Your code is used only to generate reviews for…”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Graphite✓fullclaimed8/10

   Graphite's docs explicitly state AI features are opt-in, do not train on user data, and contractually prohibit its subprocessors (Anthropic, OpenAI) from training on customer data, plus an org-wide opt-out via support request. Missing for 10: independent/third-party verification of these claims and no self-serve UI toggle (requires emailing support to disable).

   • [claimed-docs] “AI privacy and security: Graphite's AI features "are opt-in and do not store or train on your data"; "Neither Graphite nor any of its subpro…”
   • [claimed-docs] “To disable AI features across your entire organization, please email support@graphite.com and request a complete block of all AI features fo…”

   proof ↗⚑ flag

   Qodo✓fullclaimed8/10

   Qodo's pricing/FAQ page explicitly states it does not train AI models on customer code and lists 'Strict data retention' as a feature, directly addressing the no-training-data story. This is first-party vendor commitment but lacks independent/hands-on corroboration or detailed technical enforcement documentation. Missing for 10: independent verification of the no-training claim, technical/contractual details on data retention enforcement.

   • [claimed-docs] “Pricing FAQ: "Do you train AI models on my code? No. Qodo does not train models on your code. Your code is used only to generate reviews for…”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Qodo
   Graphite—none0/10

   Evidence shows a privacy statement about not training on data (opt-in, no training), but there is no mention of data retention controls, deletion mechanisms, or user-facing settings to purge stored data — the core of this story is unaddressed.

   ⚑ flag

   Qodo~partialclaimed4/10

   Qodo's pricing FAQ states it does not train models on customer code and lists 'Strict data retention' as a plan feature, and on-prem/self-hosted deployment is offered giving customers infrastructure-level control over data. However, there is no documented user-facing mechanism for explicit data deletion requests, retention period configuration, or export/erasure controls. missing for 10: explicit retention period settings, a documented data deletion/erasure workflow, independent verification of retention claims.

   • [claimed-docs] “Pricing FAQ: "Do you train AI models on my code? No. Qodo does not train models on your code. Your code is used only to generate reviews for…”
   • [claimed-docs] “This guide covers deploying Qodo in a self-managed infrastructure environment.”
   • [claimed-docs] “Deploy Qodo entirely within your own infrastructure.”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Graphite—none0/10

   Evidence covers AI-feature opt-in/no-training privacy policy (graphite-supp-1) but nothing documents a telemetry/usage-tracking opt-out mechanism for the CLI or platform itself. missing for 10: explicit telemetry/usage-analytics opt-out setting or documentation, any CLI flag or config for disabling usage tracking.

   ⚑ flag

   Qodo—none0/10

   Evidence only shows general data-usage claims (no model training on code, 'strict data retention') but nothing about a telemetry/usage-tracking opt-out setting or control. Missing for 10: any documented telemetry toggle, privacy settings page, or explicit usage-tracking opt-out mechanism.

   • [claimed-docs] “Pricing FAQ: "Do you train AI models on my code? No. Qodo does not train models on your code. Your code is used only to generate reviews for…”

   proof ↗⚑ flag

Analytics

1. engineering leadI see dashboards of findings, acceptance rates, and review coverage across my org

   weight 1 · round to Qodo
   Graphite~partialclaimed3/10

   Graphite docs reference an 'Insights' feature to 'measure and optimize your team's developer productivity' and a way to track PRs across repos, suggesting some org-level visibility, but there is no documentation describing dashboards for AI-review findings, acceptance rates of suggestions, or review-coverage metrics specifically. Missing for 10: concrete dashboard screenshots/specs for findings and acceptance-rate tracking, review-coverage metrics, and any independent corroboration of the Insights feature's content.

   • [claimed-docs] “InsightsMeasure and optimize your team's developer productivity.”
   • [claimed-docs] “Measure and optimize your team’s developer productivity.”
   • [claimed-docs] “InsightsMeasure and optimize your team’s developer productivity.”
   • [claimed-docs] “Insights Measure and optimize your team’s developer productivity.”
   • [claimed-docs] “Stay up-to-date with PRs across many repos using custom filters and rules.”

   proof ↗⚑ flag

   Qodo~partialclaimed6/10

   Qodo's code-governance docs describe org-wide history of findings/decisions, a 'Software Map' live view, and centralized rule enforcement built for engineering leaders (qodo-docs-15, qodo-docs-34, qodo-docs-38), plus risk labels for triage (qodo-docs-8/25) and org-level config controls (qodo-docs-10). However, no explicit evidence of an 'acceptance rate' metric or a 'review coverage' percentage dashboard is present — the docs describe findings history and codebase health qualitatively rather than as quantified acceptance/coverage KPIs. Missing for 10: explicit acceptance-rate metrics, explicit review-coverage percentage reporting, and independent/hands-on confirmation of the dashboard UI.

   • [claimed-docs] “See a complete history of findings, decisions, and codebase health.”
   • [claimed-docs] “Software Map gives you a live view”
   • [claimed-docs] “Qodo governance is built for engineering leaders who need consistent standards enforced across every repository, automatically, at scale, an…”
   • [claimed-docs] “Qodo makes this classification available as a native pull request tag (Azure DevOps) or label (GitHub, GitLab), so you can triage which pull…”
   • [claimed-docs] “Qodo automatically classifies the risk of a code change and can publish it as a native label in the pull request, helping teams triage which…”
   • [claimed-docs] “Organization level (default): Settings apply to all connected repositories. Repository level: Settings apply only to the selected repository…”

   proof ↗⚑ flag

Gates

1. engineering leadThe reviewer can gate merges — a required status check or blocking review that enforces resolution of critical findings

   weight 2 · round to Graphite
   Graphite~partialclaimed5/10

   Graphite offers merge queue and AI review functionality that surfaces issues, plus CI status checks via GitHub webhooks, but the evidence does not document a specific 'required status check' or 'blocking review' setting that enforces resolution of AI/critical findings before merge — the merge queue is about ordering/keeping branches green rather than gating on unresolved findings. missing for 10: explicit documentation of a required-check/blocking-review policy tied to AI review findings, admin controls to enforce this gate, and independent confirmation it blocks merges when findings are unresolved.

   • [claimed-docs] “Our stack-aware merge queue lands PRs in order and keeps branches green, helping you gain momentum.”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “Receive GitHub webhooks for real-time updates on CI status, mergeability, and push events.”
   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”

   proof ↗⚑ flag

   Qodo—none0/10

   Qodo's docs describe review findings, severity ranking, risk labels/tags for triage, and governance/standards enforcement, but nowhere document a required status check, branch-protection integration, or blocking-review mechanism that would prevent a merge until critical findings are resolved. Governance language (qodo-docs-38) speaks to standards consistency, not merge gating.

   • [claimed-docs] “Qodo makes this classification available as a native pull request tag (Azure DevOps) or label (GitHub, GitLab), so you can triage which pull…”
   • [claimed-docs] “Qodo automatically classifies the risk of a code change and can publish it as a native label in the pull request, helping teams triage which…”
   • [claimed-docs] “Qodo governance is built for engineering leaders who need consistent standards enforced across every repository, automatically, at scale, an…”
   • [claimed-docs] “every finding states what needs attention, why it matters, and how to fix it, ranked by severity”
   • [claimed-docs] “Trigger a Qodo code review manually or automatically, and control when reviews run on a pull request.”

   proof ↗⚑ flag

Detection

1. developerThe reviewer catches real bugs in my PR — logic errors, race conditions, broken edge cases — not just style nits

   weight 3 · round to Qodo
   Graphite~partialcommunity4/10

   Graphite's docs claim its AI reviewer 'identifies potential issues,' 'catches bugs,' and is 'codebase-aware,' but no evidence—vendor or independent—specifically demonstrates it catching logic errors, race conditions, or edge-case bugs versus superficial/style comments. One community comment expresses skepticism that the AI review features add lasting value, but this is general sentiment, not a concrete counter-example, so it doesn't rise to disputed. missing for 10: independent/hands-on examples of the reviewer catching genuine logic/concurrency bugs, benchmark or comparison data on false-positive/style-vs-substance ratio.

   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [community] “This is annoying, Graphite's core feature of stacked PRs is really good despite all the AI things they've added around their review UI. I do…”

   proof ↗⚑ flag

   Qodo~partialcommunity5/10

   Qodo's docs claim the reviewer surfaces 'issues that matter' with severity ranking and explanation, and reviews the full codebase (not just diff) for deeper context (qodo-docs-27, qodo-docs-22, qodo-docs-2), which supports the review-accuracy story. However, there is no independent or hands-on evidence confirming it actually catches logic errors, race conditions, or edge-case bugs specifically — all support is vendor-authored marketing copy, and one community comment reports a user dropping Qodo's review bot after two years for a competitor, hinting at unverified quality concerns without a concrete technical failure example. Missing for 10: independent benchmarks or hands-on examples of catching specific logic/concurrency bugs, third-party corroboration of low false-positive/style-nit ratio.

   • [claimed-docs] “The review focuses on surfacing issues that matter, explaining why they matter, and helping developers resolve them efficiently, without ove…”
   • [claimed-docs] “Qodo reviews the full codebase, not just the diff, to generate a structured summary of the pull request (PR) that gives reviewers meaningf”
   • [claimed-docs] “every finding states what needs attention, why it matters, and how to fix it, ranked by severity”
   • [community] “Was using their bot for code review for last 2 years but just dropped it for BugBot”

   proof ↗⚑ flag

Learning

1. developerPush back on a bad review comment and the reviewer learns — it stops repeating the same rejected feedback

   weight 2 · round to Graphite
   Graphite~partialclaimed4/10

   Graphite offers 'comment exclusions' and 'custom rules' letting developers manually configure the AI reviewer to stop leaving certain kinds of comments, which can approximate 'the reviewer learns' — but this is a manual rule-writing workaround, not an automatic learning loop triggered by pushing back in a review thread. missing for 10: evidence of automatic memory/learning from in-thread pushback, evidence that a rejected comment is not repeated without manual rule creation, any hands-on/community confirmation this actually works as claimed.

   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”

   proof ↗⚑ flag

   Qodo—none0/10

   Docs show developers can discuss or dismiss a finding (qodo-docs-3) and admins can centrally define/generate rules (qodo-docs-12, qodo-docs-13), but there is no evidence that a dismissed or pushed-back finding is remembered and suppressed in future reviews of similar code — i.e., no documented feedback loop that stops the reviewer from repeating the same rejected comment. Missing for 10: any documentation of per-finding dismissal memory, learning from rejected feedback, or reduced recurrence of the same flagged issue after pushback.

   • [claimed-docs] “Discuss or dismiss a finding, or let Qodo apply the fix directly.”
   • [claimed-docs] “Define and enforce engineering standards with a centralized rule system.”
   • [claimed-docs] “Generate rules from pull request history with Rule Miner”

   proof ↗⚑ flag

Noise

1. engineering leadThe reviewer keeps noise low — few false positives, deduplicated comments, severity labels — so my team doesn't tune it out

   weight 3 · round to Qodo
   Graphite~partialcommunity5/10

   Graphite lets teams reduce noise via custom rules and comment exclusions (specifying when Agent should not comment) and codebase-aware review context, which addresses false positives to some degree, but there is no documented deduplication mechanism or severity/priority labeling on comments, and community reaction (e.g. mixed sentiment about the AI review additions) is vague rather than a concrete accuracy failure. missing for 10: explicit severity/priority labeling of comments, deduplication logic across review passes, independent benchmarking or hands-on evidence of false-positive rates.

   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should **not** leave comments.”
   • [claimed-docs] “Get immediate, actionable feedback with Graphite’s codebase-aware AI code review agent.”
   • [community] “This is annoying, Graphite's core feature of stacked PRs is really good despite all the AI things they've added around their review UI. I do…”
   • [community] “i mentioned a few months ago that it was a shame where graphite was headed re: AI... this appears to be the final nail in the original produ…”

   proof ↗⚑ flag

   Qodo~partialcommunity6/10

   Qodo's docs explicitly claim severity-ranked findings, low-signal filtering ('surfacing issues that matter... without overwhelming you with low-signal feedback'), risk/blast-radius labels for triage, and configurable display presets (Minimal/Standard/Comprehensive) that let teams tune noise. However there's no explicit 'deduplication' feature documented, and no independent/hands-on evidence confirming actual false-positive rates in practice — one community comment even reports a team abandoning Qodo's review bot for a competitor, though not specifically citing noise as the reason. missing for 10: explicit deduplication mechanism, independent benchmark or user testimonial confirming low false-positive rate in real-world use.

   • [claimed-docs] “every finding states what needs attention, why it matters, and how to fix it, ranked by severity”
   • [claimed-docs] “The review focuses on surfacing issues that matter, explaining why they matter, and helping developers resolve them efficiently, without ove…”
   • [claimed-docs] “Qodo makes this classification available as a native pull request tag (Azure DevOps) or label (GitHub, GitLab), so you can triage which pull…”
   • [claimed-docs] “Qodo automatically classifies the risk of a code change and can publish it as a native label in the pull request, helping teams triage which…”
   • [claimed-docs] “Choose a ready-made preset, Minimal, Standard, Comprehensive, or Custom, instead of setting each Display option individually.”
   • [community] “Was using their bot for code review for last 2 years but just dropped it for BugBot”

   proof ↗⚑ flag

Security

1. security engineerReviews flag security problems in the diff — injection risks, leaked secrets, insecure patterns — alongside functional bugs

   weight 2 · round to Qodo
   Graphite—none0/10

   Graphite's AI review docs describe catching 'bugs' and general 'potential issues' in PRs, but nothing in the evidence pack specifically claims detection of security-specific problems like injection risks, leaked secrets, or insecure coding patterns; custom rules/comment exclusions are the only customization levers mentioned, not security-focused presets.

   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “AI reviews powered by Graphite Agent help your team build better software by automatically reviewing pull requests and catching bugs before …”
   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”

   proof ↗⚑ flag

   Qodo~partialclaimed5/10

   Qodo's docs describe automated PR reviews that flag findings with severity, explanations, and fixes, and generally aim to surface 'issues that matter' beyond just functional bugs, but the evidence never explicitly confirms detection of security-specific issues like injection risks or leaked secrets. missing for 10: explicit documentation of security-issue detection (secrets scanning, injection/insecure-pattern flags), independent/hands-on confirmation that security findings actually appear in review output.

   • [claimed-docs] “every finding states what needs attention, why it matters, and how to fix it, ranked by severity”
   • [claimed-docs] “The review focuses on surfacing issues that matter, explaining why they matter, and helping developers resolve them efficiently, without ove…”
   • [claimed-docs] “Qodo is an AI code review platform that provides automated”
   • [claimed-docs] “Qodo makes this classification available as a native pull request tag (Azure DevOps) or label (GitHub, GitLab), so you can triage which pull…”

   proof ↗⚑ flag

Cli

1. developerI run reviews from a CLI against local diffs or in CI scripts, with machine-readable output my tooling can consume

   weight 2 · round to Qodo
   Graphite—none0/10

   Graphite's AI review capability is documented as PR-triggered via the GitHub App/web UI (automatically reviewing pull requests), not as a CLI command usable against local diffs or in CI scripts with machine-readable output. The `gt` CLI documented is for stack management (branch creation, submission, config) with no review subcommand or structured/JSON output format mentioned anywhere in the evidence.

   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization.”
   • [claimed-docs] “The Graphite CLI is a tool to help you break up large engineering tasks into a series of small, incremental code changes directly from the c…”
   • [claimed-docs] “Run gt config to open an interactive menu which lets you configure your Graphite CLI.”

   proof ↗⚑ flag

   Qodo~partialprobed5/10

   Qodo documents an official Agentic Toolbox CLI that can 'review changes before opening a pull request' (local diffs) and retrieve findings/rules (qodo-docs-5, qodo-docs-6, qodo-docs-7, qodo-probe-4), showing CLI-based local review support. However, there is no documentation of CI-script invocation patterns or machine-readable (JSON/SARIF) output formats for tooling consumption. Missing for 10: explicit CI/script usage examples, documented machine-readable output format, and independent confirmation of CLI output structure.

   • [claimed-docs] “Review changes before opening a pull request.”
   • [claimed-docs] “Retrieve and resolve review findings.”
   • [claimed-docs] “Retrieve the rules and standards that apply to a task.”
   • [probe] “official CLI documented at https://docs.qodo.ai/agentic-toolbox/cli”

   proof ↗⚑ flag

Ide

1. developerI get the same review inside my IDE before I push, catching issues while the code is still in my editor

   weight 2 · round to Qodo
   Graphite—none0/10

   Graphite's AI review (Agent) explicitly runs on pull requests after they are opened on GitHub, not inside the IDE before push; the only 'IDE' touchpoint documented is a GUI for visualizing stacks, not a pre-push review mechanism. No evidence of an IDE plugin or pre-commit hook that surfaces the same AI review before pushing.

   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”
   • [claimed-docs] “A GUI designed to make stacking visual and simple, right from your IDE.”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”

   proof ↗⚑ flag

   Qodo~partialprobed6/10

   Qodo's Agentic Toolbox (CLI, MCP, and plugins for Claude Code/Codex/Kiro) explicitly supports 'review changes before opening a pull request' using the same review/coding-standards engine as PR review, which lets a developer catch issues pre-push in their coding environment. However, this is delivered via CLI/agent plugins rather than a dedicated native IDE extension, and there's no evidence confirming parity of findings between local pre-push reviews and PR reviews. Missing for 10: a first-party IDE extension (VS Code/JetBrains) with inline review, and independent confirmation that local/CLI review output matches PR review quality.

   • [claimed-docs] “Review changes before opening a pull request.”
   • [claimed-docs] “The Qodo Agentic Toolbox brings Qodo's code understanding, coding standards, and review capabilities into your existing coding agent.”
   • [claimed-docs] “Use Qodo with Claude to access Qodo Agentic Toolbox skills for understanding your codebase, reviewing changes, and resolving code review fin…”
   • [claimed-docs] “Use the Qodo plugin with the Codex agent to access Qodo Agentic Toolbox skills for understanding your codebase, reviewing changes, and resol…”
   • [claimed-docs] “Use Qodo with the Kiro agent to access Qodo Agentic Toolbox skills for understanding your codebase, reviewing changes, and resolving code re…”
   • [claimed-docs] “Use the Qodo Agentic Toolbox CLI when you want to use Qodo-managed skills locally.”
   • [probe] “official CLI documented at https://docs.qodo.ai/agentic-toolbox/cli”

   proof ↗⚑ flag

Config

1. engineering leadI configure the reviewer with a versioned config file in my repo — path filters, per-path instructions, review profiles

   weight 3 · round to Qodo
   Graphite~partialclaimed5/10

   Graphite supports custom rules and comment exclusions for the AI review agent (graphite-docs-5, graphite-docs-20), which covers per-repo instruction customization, but there is no evidence of a versioned config file checked into the repo, nor of path-based filters or multiple named review profiles selectable per path. missing for 10: evidence of a repo-committed/versioned config file format, path-level filtering rules, and support for multiple distinct review profiles.

   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “AI reviews can be enabled in just a few clicks, with no configuration required to start catching bugs in your pull requests.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”

   proof ↗⚑ flag

   Qodo~partialclaimed6/10

   Qodo documents a versioned configuration-as-code file (.pr_agent.toml) that can be set at repository, project, group, or org level, plus an org/repo-level portal configuration hierarchy and a centralized rule system for engineering standards. However, the evidence does not explicitly confirm path-based filters or per-path instructions within that file, and the only 'profile' concept shown (Minimal/Standard/Comprehensive/Custom presets) applies to display options rather than a full review-profile system. Missing for 10: explicit documentation of path/glob filters, per-path instruction blocks, and named review profiles beyond display presets.

   • [claimed-docs] “Manage Qodo configuration as code using a .pr\_agent.toml file at the repository, project, group, or organization level.”
   • [claimed-docs] “Manage Qodo configuration as code using a .pr_agent.toml file at the repository, project, group, or organization level.”
   • [claimed-docs] “Organization level (default): Settings apply to all connected repositories. Repository level: Settings apply only to the selected repository…”
   • [claimed-docs] “Define and enforce engineering standards with a centralized rule system.”
   • [claimed-docs] “Choose a ready-made preset, Minimal, Standard, Comprehensive, or Custom, instead of setting each Display option individually.”

   proof ↗⚑ flag

Governance

1. engineering leadI roll out org-level review defaults across hundreds of repos and manage exceptions centrally

   weight 1 · round to Qodo
   Graphite~partialclaimed5/10

   Graphite supports org-wide GitHub App installation and enabling AI review across 'selected repositories' with per-repo custom rules and comment exclusions, and org-wide AI-disable requires emailing support — but there is no documented centralized dashboard for setting org-level review defaults and managing per-repo exceptions at scale across hundreds of repos. missing for 10: evidence of a bulk/org-level policy management UI, audit of exceptions across many repos, and any customer testimonial about managing hundreds of repos centrally.

   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization.”
   • [claimed-docs] “Graphite Agent will now automatically review all new pull requests in the selected repositories”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should **not** leave comments.”
   • [claimed-docs] “To disable AI features across your entire organization, please email support@graphite.com and request a complete block of all AI features fo…”
   • [claimed-docs] “you'll need to authenticate by installing the Graphite App (a GitHub App) on your organization”

   proof ↗⚑ flag

   Qodo✓fullclaimed8/10

   Docs directly address org-level defaults with repo-level exceptions (qodo-docs-10: org-level default settings applying to all connected repos, with repo-level overrides), configuration-as-code across repository/project/group/organization scope (qodo-docs-11/36), a centralized rule system for engineering standards (qodo-docs-12), and explicit governance framing for consistent enforcement at scale across every repo (qodo-docs-38). A portal-based Configurations UI is also documented as the recommended management path (qodo-docs-35). Missing for 10: independent/hands-on evidence of this working across hundreds of repos in practice, and more detail on exception-approval workflows beyond simple repo-level override.

   • [claimed-docs] “Organization level (default): Settings apply to all connected repositories. Repository level: Settings apply only to the selected repository…”
   • [claimed-docs] “Manage Qodo configuration as code using a .pr\_agent.toml file at the repository, project, group, or organization level.”
   • [claimed-docs] “Define and enforce engineering standards with a centralized rule system.”
   • [claimed-docs] “The recommended way to manage organization-wide and repository-level code review configuration, from the Configurations page in the Qodo por…”
   • [claimed-docs] “Manage Qodo configuration as code using a .pr_agent.toml file at the repository, project, group, or organization level.”
   • [claimed-docs] “Qodo governance is built for engineering leaders who need consistent standards enforced across every repository, automatically, at scale, an…”

   proof ↗⚑ flag

Rules

1. engineering leadI encode my team's own review guidelines — natural-language rules, AST patterns, or linked style guides — and the reviewer enforces them

   weight 2 · round to Qodo
   Graphite~partialclaimed6/10

   Graphite's AI review docs confirm a 'Custom rules' feature letting teams define explicit natural-language guidelines for the review agent, plus 'comment exclusions' to tune behavior, which covers the natural-language rules part of the story. However, there is no evidence of AST-pattern-based rule definition or linking external/style-guide documents for enforcement. Missing for 10: AST pattern rule support, ability to link external style guides, and independent/hands-on confirmation that custom rules are reliably enforced.

   • [claimed-docs] “Custom rules allow you to define explicit guidelines for Graphite Agent to follow when reviewing your code.”
   • [claimed-docs] “Comment exclusions allow you to specify situations where Graphite Agent should not leave comments.”
   • [claimed-docs] “AI reviews analyze every pull request in your repositories, identifying potential issues and suggesting fixes instantly - no manual configur…”

   proof ↗⚑ flag

   Qodo~partialclaimed7/10

   Qodo documents a centralized rule system for defining/enforcing engineering standards, a Rule Miner that generates rules from PR history, and configuration-as-code via .pr_agent.toml or portal-level settings that apply org- or repo-wide, plus an Agentic Toolbox capability to 'retrieve rules and standards that apply to a task.' This covers natural-language rule encoding and centralized enforcement well, but there is no explicit evidence of AST-pattern-based rule definitions or linking external style guide documents specifically. Missing for 10: explicit AST-pattern rule support, direct linking/import of external style guide docs, and independent/hands-on confirmation that custom rules are reliably enforced in reviews.

   • [claimed-docs] “Retrieve the rules and standards that apply to a task.”
   • [claimed-docs] “Manage Qodo configuration as code using a .pr\_agent.toml file at the repository, project, group, or organization level.”
   • [claimed-docs] “Define and enforce engineering standards with a centralized rule system.”
   • [claimed-docs] “Generate rules from pull request history with Rule Miner”
   • [claimed-docs] “The recommended way to manage organization-wide and repository-level code review configuration, from the Configurations page in the Qodo por…”
   • [claimed-docs] “Manage Qodo configuration as code using a .pr_agent.toml file at the repository, project, group, or organization level.”

   proof ↗⚑ flag