ollama-result-handling

Internal guidance for presenting Ollama helper output back to the user

Repositorio: darrylmorley/ollama-plugin-cc
Última actividad en el origen: 30 de abril de 2026 a las 16:40
Idioma detectado de SKILL.md: inglés
Estrellas: 4
Forks: 0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/darrylmorley/ollama-plugin-cc --skill ollama-result-handling

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

ollama-cli-runtime

Internal helper contract for calling the ollama-companion runtime from Claude Code

2026-05-01

ollama-model-prompting

Guidance on selecting and prompting open-weight Ollama models for review and rescue tasks

2026-05-01

Ver todos los de este repositorio

Ollama Result Handling

When the helper returns Ollama 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 Ollama 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 Ollama made edits, say so explicitly and list the touched files when the helper provides them.

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

For ollama:ollama-rescue, if Ollama 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 Ollama run, include the most actionable stderr lines and stop there instead of guessing.

If Ollama returns malformed JSON despite JSON-mode being enabled, surface the raw response verbatim with a clear error label ("Ollama returned malformed JSON:") rather than trying to extract or infer fields from it. Prompt the user to retry with a stronger model or to run /ollama:review --wait manually.

If the helper reports that setup or authentication is required, direct the user to /ollama:setup and do not improvise alternate auth flows.