Skill

gemini-result-handling

Internal guidance for presenting Gemini helper output back to the user

Install

Run in your terminal

npx claudepluginhub abiswas97/gemini-plugin-cc --plugin gemini

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

istio-traffic-management

Configures Istio traffic management with VirtualServices, DestinationRules for routing, canary/blue-green deployments, circuit breakers, load balancing, and fault injection in service meshes.

cloud-infrastructure

33.0k

Stats

Parent Repo Stars3

Parent Repo Forks0

Last CommitMar 31, 2026

Actions

View Source View Plugin View on GitHub View README

Gemini Result Handling

When the helper returns Gemini output:

Preserve the helper's verdict, summary, findings, and next steps structure.

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.

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.

For gemini:gemini-rescue, do not turn a failed or incomplete Gemini run into a Claude-side implementation attempt. Report the failure and stop.

For gemini:gemini-rescue, if Gemini was never successfully invoked, do not generate a substitute answer at all.

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.

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.

Gemini Result Handling

When the helper returns Gemini output:

Preserve the helper's verdict, summary, findings, and next steps structure.
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.
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.
For gemini:gemini-rescue, do not turn a failed or incomplete Gemini run into a Claude-side implementation attempt. Report the failure and stop.
For gemini:gemini-rescue, if Gemini was never successfully invoked, do not generate a substitute answer at all.
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.
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.