Library · Team · Ollama · coding-review
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 recipe is a local AI agent / local AI workflow for the parent AI Team. It is a single-prompt (or system-prompt) recipe — 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
- You will run this locally or on infra you control.
- No production credentials in prompts or committed files.
- Ollama installed
- A local instruct model pulled
How to use
- Install Ollama and pull a base model you already trust (example: llama3.2).
- Save the Modelfile above in an empty folder.
- Run: ollama create botshelf-coding-review -f Modelfile
- Run: ollama run botshelf-coding-review
- Paste your input (see Example in). Expect the structured output; then stop.
- Note: llama3.2:1b showed invent/numeric failures in Proof Engine — prefer full llama3.2 (3B+) for coding-review/data-analysis.
Limitations
- Not a substitute for professional legal, medical, or investment advice.
- Outputs can be wrong; human review required before publish or spend.
- Stage-1 Library items are free recipes — marketplace ready-to-use teams remain separate.
- Local models may omit sections; re-prompt once if needed.
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.
Files
Modelfile— Create a local model with the system promptprompt.md— User-facing run instructions
Full prompt / config / code
Free. No sign-up. The full text is right here. Copy it, or take the file with you.
無料・登録不要。全文はこの下にあります。コピーするか、ファイルで持ち帰れます。
Download .md.md で持ち帰る How to run it動かし方 Fork itフォークする Results & questions結果・質問を書く
# 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. - Always emit ALL four OUTPUT sections. - Severity must be Critical|High|Med|Low. - Do not invent file paths, APIs, CVEs, try/except, env-var usage, or other controls not literally in the paste. - If a secret is hardcoded in the paste, list it under Issues; under "What looks fine" you MUST NOT praise environment-variable secret storage or claim secrets are handled safely. - "What looks fine" may only name behaviors/lines that are literally present in the paste. If unsure, write "None noted without inventing." - Do not contradict Issues in What looks fine. - 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 # # Model note: llama3.2:1b showed invent/numeric failures in Proof Engine; # prefer full llama3.2 (3B+) for coding-review/data-analysis. Keep FROM llama3.2 # as-is (matches Library). # # Safety: no network tools required. Do not pass API keys into the Modelfile.
License as listed in the registry: free-use-at-own-risk. Use is at your own risk. BSV does not run it for you. What is open here
ライセンス(レジストリの記載どおり):free-use-at-own-risk。 利用は自己責任です。BSVが代わりに実行することはありません。何が開いているか
This job is also written for 6 other tools. See all 7 versions side by side.
この仕事は、ほかに 6 のツール向けの版があります。7 版を並べて見る。
Example in
Review this Python snippet:
```
def pay(user, amount):
charge(user.card, amount)
send_receipt(user.email)
```
Context: internal tool, no retries yet.Example out
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.
Model / runtime notes
FROM llama3.2 (Library default). llama3.2:1b showed invent/numeric failures in Proof Engine; prefer full llama3.2 (3B+) for coding-review/data-analysis. Works best with 8k+ context instruct models. Smaller models may skip sections — ask it to continue once.
Canonical Team
Parent: coding-review
· implementation_id: ollama/coding-review
GitHub source
teams/coding-review/ollama (path in the BSV team registry repository) · commit eb87e8e049fdf9908e438305ff827c7b617505b5
· license: free-use-at-own-risk
Structural check: PASS · env: structural (structural only — does not set Verified)
Related Library items
Related marketplace Team pages
Soft thematic links only — not identity merges. Marketplace Teams ≠ Library AI Team records.
- Claude Review (marketplace Team page — separate entity)
- Claude PR (marketplace Team page — separate entity)