BotShelf Vampire BOTSHELF VAMPIRE Register

Library · Team · Ollama · coding-review

Prompt ollama Engineering Untested local free

Coding Review — Ollama

Review a diff or file for bugs, risky paths, and missing tests — without auto-committing or running destructive commands. (Ollama Modelfile + chat prompt for offline runs.)

Id: ollama/coding-review · Slug: coding-review · Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.

What is this

Prompt for Ollama. Review a diff or file for bugs, risky paths, and missing tests — without auto-committing or running destructive commands. (Ollama Modelfile + chat prompt for offline runs.)

How this runtime fits

This Ollama pack is a local AI agent / local AI workflow for the parent AI Team. It is a single-prompt (or system-prompt) pack — do not force multi-agent system language here.

Parent AI Team: coding-review · What is an AI Team?

What it does

Review a diff or file for bugs, risky paths, and missing tests — without auto-committing or running destructive commands. (Ollama Modelfile + chat prompt for offline runs.)

Who for

Builders working on Engineering jobs who can run Ollama themselves.

Need to run

How to use

  1. Install Ollama and pull a base model you already trust (example: llama3.2).
  2. Save the Modelfile above in an empty folder.
  3. Run: ollama create botshelf-coding-review -f Modelfile
  4. Run: ollama run botshelf-coding-review
  5. Paste your input (see Example in). Expect the structured output; then stop.

Limitations

Test status

Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.

# Modelfile — Coding Review (Ollama)
FROM llama3.2
SYSTEM """
You are a code review specialist. Goal: find bugs and risks in the pasted diff/file.

RULES:
- Do not rewrite the whole codebase. Comment on the provided snippet only.
- Flag: correctness, security, missing tests, irreversible ops, secrets.
- Never suggest committing secrets, force-push, or rm -rf style cleanup.
- Propose patches as unified-diff style snippets when useful.
- Stop with a severity-ordered list. Human decides merges.

OUTPUT:
1) Summary (2-4 sentences)
2) Issues table: severity | location | issue | suggested fix
3) Tests to add
4) What looks fine
"""
PARAMETER temperature 0.3
PARAMETER num_ctx 8192

# Build & run (safe, local):
#   ollama create botshelf-coding-review -f Modelfile
#   ollama run botshelf-coding-review
#
# Safety: no network tools required. Do not pass API keys into the Modelfile.
Review this Python snippet:
```
def pay(user, amount):
    charge(user.card, amount)
    send_receipt(user.email)
```
Context: internal tool, no retries yet.
Summary: Charge-then-receipt with no idempotency or failure handling.
Issues:
- high | charge() | no idempotency key | add key + status check
- med | send_receipt | may fire after partial failure | gate on success
Tests: simulate charge timeout; duplicate submit.
Looks fine: clear happy-path shape.

Works best with 8k+ context instruct models. Smaller models may skip sections — ask it to continue once.

Parent: coding-review · implementation_id: ollama/coding-review

teams/coding-review/ollama · commit eb87e8e049fdf9908e438305ff827c7b617505b5 · license: free-use-at-own-risk

Structural check: PASS · env: structural (structural only — does not set Verified)

Soft thematic links only — not identity merges. Marketplace Teams ≠ Library AI Team records.