gerrit-task-query

Gerrit Task Query

The Gerrit task plugin attaches a task tree to each change. Tasks represent CI checks, review requirements, and dependency gates. This skill shows how to fetch the task tree, find tasks that need action, and determine what to do.

The tools get_task_tree and get_actionable_tasks are provided by the gerrit_mcp_server_task extension (entry point gerrit_mcp_server.extensions). They are available whenever gerrit-mcp-server is running with the task extension installed and a configured Gerrit host that has the task plugin enabled.

1. Fetch tasks for a change

Task plugin options (task--applicable, task--only, etc.) are Gerrit DynamicOptions — they are passed as direct HTTP query parameters (&task--applicable), not as standard Gerrit output options (&o=).

Using the MCP tools (preferred — returns structured task tree JSON):

# All applicable tasks for a change
get_task_tree(change_id="123")

# Scope to one root task
get_task_tree(change_id="123", task_only="Jenkins")

# Convenience: returns only READY and FAIL nodes, pre-walked
get_actionable_tasks(change_id="123")
get_actionable_tasks(change_id="123", task_only="Jenkins")

Using query_changes / get_change_details (plain-text summary only):

# These pass task parameters but only return a text summary — use the task tools above instead
query_changes(query="change:123", parameters={"task--applicable": None})
get_change_details(change_id="123", parameters={"task--applicable": None})

2. Task node fields

Field	Meaning
name	Task name
status	Status value (see table below)
hint	Human-readable explanation (present on READY and FAIL)
in_progress	true if task is currently executing
has_pass	true if the task has a terminal pass/fail condition
exported	Custom key-value metadata from the task definition
change	Change number — only on tasks generated by a change-type tasks-factory
sub_tasks	Child task nodes (recursive, arbitrary depth)