gemini-result-handling

Gemini Result Handling

When the helper returns Gemini output:

• Preserve the helper's structure and fidelity. Do not paraphrase, reorder, or drop sections.
• For review output, present findings first and keep them ordered by severity.
• Use the file paths and line numbers exactly as the helper reports them.
• Preserve evidence boundaries. If Gemini marked something as an inference, uncertainty, or follow-up question, keep that distinction.
• Preserve output sections when the prompt asked for them, such as observed facts, inferences, open questions, touched files, or next steps.
• Preserve verdicts, line numbers, and confidence scores exactly as reported. Do not round, reinterpret, or editorialize numeric values.
• If there are no findings, say that explicitly and keep the residual-risk note brief.
• If Gemini made edits, say so explicitly and list the touched files when the helper provides them.

Review-specific rules:

• CRITICAL: After presenting review findings, STOP. Do not make any code changes. Do not fix any issues. You MUST explicitly ask the user which issues, if any, they want fixed before touching a single file. Auto-applying fixes from a review is strictly forbidden, even if the fix is obvious.

Search-specific rules:

• Preserve all citations and source URLs exactly as Gemini reports them.
• Keep sources grouped and ordered by relevance when the helper provides a ranking.
• Do not strip, rewrite, or shorten source URLs.
• Preserve the confidence score for the overall search result.

Analyze-specific rules:

• Preserve multimodal analysis details including observations about images, audio, video, and documents.
• Keep file-type-specific observations intact. Do not merge observations from different files into a single generic summary.
• Preserve any extracted text, transcriptions, or structured data from the analyzed files.

Failure handling:

• For gemini:gemini-delegate, do not turn a failed or incomplete Gemini run into a Claude-side implementation attempt. Report the failure and stop.
• For gemini:gemini-delegate, if Gemini was never successfully invoked, do not generate a substitute answer at all.
• If the helper reports malformed output or a failed Gemini run, include the most actionable stderr lines and stop there instead of guessing.
• If the helper reports that setup or authentication is required, direct the user to /gemini:setup and do not improvise alternate auth flows.
• Report failures without substitution. Do not invent results to replace a failed Gemini call.

Formatting rules:

• Format findings in a readable table or list grouped by severity.
• Use markdown formatting for file paths, line numbers, and code references.
• Keep the summary concise but preserve all actionable detail from the helper output.
• For search results, format sources as a numbered list with title, URL, and snippet.
• For analysis results, use headings per analyzed file when multiple files are present.