mergetai/merget

Queries Merget's code property graphs of any commit in a repository where Merget is installed — symbols in a file, callers and callees, def-use chains, program dependence slices, the graph diff between two commits, a finding's slice, and a PR side's intent — through the merget_graph_* MCP tools. Use when the user asks what calls or is called by a function, where a variable is defined or used, what a change reaches or depends on, what will break if a PR merges, why a Merget finding exists, what a PR or its target branch actually changed at the symbol level, for a slice or dependence context around a line, or for callers/callees/def-use/slice/graph diff on a commit, branch, or pr:N:head/pr:N:base/pr:N:merge revision; also use to confirm a syntactic Merget finding before acting on it.

Operates Merget as its dashboard does, short of an owner's steps, through the merget MCP server — repository settings, the merge queue (merget_queue_get, merget_batch, merget_queue_action), runs, analytics, the organization and its members (read-only), installation re-checks, validation secrets and the docs. Use when the user asks to change a Merget setting (mode, target branch, merge method, batching, passing lane, Layer 2, validation, generated files, CI checks, C parsing, the verified branch), to retry, hold or release a pull request, merge what's ready, land, merge anyway over failing CI, cancel a land request, fix a failed batch, resolve a pull request's conflicts for merge time, dismiss a finding, for runs, analytics, credits, members, repository secrets or the docs; and when asked to pause or resume a queue, rename the organization, change its billing, change members, organization secrets or strict protection, which stay the human's. First setup is merget-setup's; findings are merget-pr's.

Reads and interprets Merget's analysis of a GitHub pull request (findings, verdict, brief, queue position, enforcement state, credits) through the merget MCP server. Use when the user mentions Merget, a Merget check, a Merget finding or comment on a PR, a merge queue verdict, "would block", blocking or advisory findings, broken references, interference between branches, Layer 1 / Layer 2 findings, provenance (precise / syntactic), shadowed or suppressed findings, review findings, textual conflicts (with the target or with a pull request ahead in the queue), a merge brief, queue rank or position, queue enforcement, or asks whether a pull request is safe to merge, why a PR is blocked or held, what Merget found on a PR, what to fix before merging, or what will break when a PR lands, or what a PR cost in Merget credits; also use before reviewing, fixing, rebasing or merging a pull request in a repository where Merget is installed.

Sets Merget up for the user, from the first call to a repository Merget works on, through the merget MCP server — who the agent acts for and with which permissions (merget_status), handing the human the dashboard page where they connect GitHub (the next step merget_status names; an owner's step, never an agent's), re-checking an installation (merget_installation_sync), enabling a first repository (merget_repos_list, merget_repo_update) and choosing its automation mode from the readiness verdict (merget_repo_settings_get). Use when the user asks to set up, onboard, connect or install Merget, to connect GitHub to Merget, to enable Merget on a repository, to choose advisory, queue or autonomous mode, where Merget's setup stands or what to do next, or why Merget shows no repositories; when a setup prompt from sema.merget.ai says so; and when a Merget tool answers insufficient_scope, agent_scope_disabled, agent_access_disabled, not_a_member or no_organization.