Skill

gemini-result-handling

Internal guidance for presenting Gemini helper output back to the user

npx claudepluginhub josephyaduvanshi/gemini-companion --plugin gemini

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/gemini:gemini-result-handling

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

When the helper returns Gemini output:

SKILL.md

22 lines · ~438 tokens

Similar Skills

cache-components

139.6k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

claude-opus-4-5-migration

124.6k

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.

2 files

claude-opus-4-5-migration

to-issues

96.3k

Breaks plans, specs, or PRDs into thin vertical-slice issues on the project issue tracker using tracer bullets. Useful for converting high-level work into grabbable implementation tickets.

mattpocock-skills

Stats

LanguageJavaScript

Parent stars0

MaintenanceGood

Last CommitApr 15, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Gemini Result Handling

When the helper returns Gemini output:

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

For review-style 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.