Tool tree
gradeNot graded
page: Every page
search_gitwand_docsAnswer
Search the GitWand documentation for guides, API reference, CLI commands, and blog articles.
View tool JSON
{
"name": "search_gitwand_docs",
"kind": "answer",
"impl": "imperative",
"description": "Search the GitWand documentation for guides, API reference, CLI commands, and blog articles.",
"inputSchema": {
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Search terms"
}
},
"required": [
"query"
]
},
"page": "/agent"
}get_gitwand_mcp_installAnswer
Get the installation instructions and configuration snippet for GitWand MCP server.
View tool JSON
{
"name": "get_gitwand_mcp_install",
"kind": "answer",
"impl": "imperative",
"description": "Get the installation instructions and configuration snippet for GitWand MCP server.",
"inputSchema": {
"type": "object",
"properties": {}
},
"page": "/agent"
}navigate_to_gitwand_sectionAction
Get the URL for a GitWand documentation section.
View tool JSON
{
"name": "navigate_to_gitwand_section",
"kind": "act",
"impl": "imperative",
"description": "Get the URL for a GitWand documentation section.",
"inputSchema": {
"type": "object",
"properties": {
"section": {
"type": "string",
"enum": [
"getting-started",
"desktop",
"cli",
"ai",
"mcp",
"vscode",
"conflict-resolution",
"core-api",
"config",
"cli-commands",
"changelog",
"blog"
],
"description": "Documentation section to navigate to"
}
},
"required": [
"section"
]
},
"page": "/agent"
}page: Agent
resolve_conflictAction
Resolve a file containing git conflict markers, and file it into the Merge Room on this page. Hunks that carry no real decision (identical edits on both sides, pure reordering, whitespace, insertions at different positions, generated files) are resolved deterministically. Hunks where the two branches genuinely disagree are NOT resolved: they queue for the person at the page to pick a side, and this tool cannot make that call. Returns a per-hunk classification with the pattern name, confidence score and reason for each. No model is involved and nothing is guessed. Runs in the browser tab: the file content is never uploaded.
View tool JSON
{
"name": "resolve_conflict",
"kind": "act",
"impl": "imperative",
"description": "Resolve a file containing git conflict markers, and file it into the Merge Room on this page. Hunks that carry no real decision (identical edits on both sides, pure reordering, whitespace, insertions at different positions, generated files) are resolved deterministically. Hunks where the two branches genuinely disagree are NOT resolved: they queue for the person at the page to pick a side, and this tool cannot make that call. Returns a per-hunk classification with the pattern name, confidence score and reason for each. No model is involved and nothing is guessed. Runs in the browser tab: the file content is never uploaded.",
"inputSchema": {
"type": "object",
"properties": {
"content": {
"type": "string",
"description": "The complete conflicted file, including the <<<<<<<, ======= and >>>>>>> markers. Pass the whole file, not just the conflicted region."
},
"filePath": {
"type": "string",
"description": "Path of the file, e.g. \"src/config.json\" or \"pnpm-lock.yaml\". This changes the result: the extension selects format-aware resolvers (JSON, YAML, TypeScript imports, Vue SFC, CSS, lockfiles) and the path is what identifies a generated file. Pass the real path when you have it."
}
},
"required": [
"content"
]
},
"page": "/agent"
}parse_git_errorAction
Explain a git command that failed, and file it into the Merge Room on this page so the person watching sees it. Paste the raw stderr or stdout of the failing command and get back the cause in plain language plus the specific commands that resolve it. Handles merge conflicts, rejected pushes, unrelated histories, detached HEAD, an interrupted merge, rebase or cherry-pick, authentication failures and other common git errors. Read-only: it never runs git and never touches the repository.
View tool JSON
{
"name": "parse_git_error",
"kind": "act",
"impl": "imperative",
"description": "Explain a git command that failed, and file it into the Merge Room on this page so the person watching sees it. Paste the raw stderr or stdout of the failing command and get back the cause in plain language plus the specific commands that resolve it. Handles merge conflicts, rejected pushes, unrelated histories, detached HEAD, an interrupted merge, rebase or cherry-pick, authentication failures and other common git errors. Read-only: it never runs git and never touches the repository.",
"inputSchema": {
"type": "object",
"properties": {
"output": {
"type": "string",
"description": "The raw output of the failing git command, copied verbatim. Multiple errors in one paste are all reported."
}
},
"required": [
"output"
]
},
"page": "/agent"
}list_casesAnswer
Read the current state of the Merge Room on this page: every conflict and git error filed so far, which hunks the engine settled, which are still waiting on a human decision, and which the human has already decided. Call this to see what is outstanding before deciding what to do next, or after asking the person to make a call. Takes no arguments.
View tool JSON
{
"name": "list_cases",
"kind": "answer",
"impl": "imperative",
"description": "Read the current state of the Merge Room on this page: every conflict and git error filed so far, which hunks the engine settled, which are still waiting on a human decision, and which the human has already decided. Call this to see what is outstanding before deciding what to do next, or after asking the person to make a call. Takes no arguments.",
"inputSchema": {
"type": "object",
"properties": {}
},
"page": "/agent"
}