Ai-Coding

You can wire a local LLM into your Git workflow to write conventional commit messages from staged diffs. The trick is a prepare-commit-msg Git hook. The hook runs git diff --cached and sends the output to Ollama . Ollama runs a model like Llama 4 Scout on a consumer GPU or Qwen3, then writes the message into the commit file for you to review. The whole setup is about 30 lines of shell or Python. It costs nothing to run, keeps your code local, and follows the Conventional Commits format. That beats the “fix stuff” messages most of us write when we just want to move on.

Qwen 2.5 Coder 7B is the most accurate of the three for Python and TypeScript completions. Phi-4 Mini (3.8B) uses the least VRAM and runs nearly twice as fast. Pick it when memory or latency counts more than raw accuracy. Gemma 3 4B sits in the middle. It is the best choice when you need one model for code, commit messages, docs, and error explanations. Below are the benchmark numbers, the test method, and how to set up each model in VS Code or Neovim.

You can plug a local LLM into your Gitea Actions, or any CI system, to review pull requests on its own. The pipeline pulls the diff, feeds it to a model running on Ollama , and posts structured feedback as PR comments. No code ever leaves your network. The setup needs three parts: a self-hosted runner with GPU access, a review prompt template, and a short Python wrapper.

Why Local LLM Code Reviews Make Sense

Static analysis tools like ESLint , Ruff , and Semgrep are great at catching syntax errors, style slips, and known vulnerability patterns. What they miss are logic bugs, unclear variable names, missing edge cases, and design concerns. An LLM fills that gap because it reads code in context. It can tell you that a function does the wrong thing, not just that it’s formatted wrong.

Claude Opus 4.7 landed on April 16, 2026, and after the first 48 hours on X and Reddit the verdict is net-positive but heavily qualified. Power users are calling it state-of-the-art for agentic coding, long refactors, and the viral new Claude Design tool. The loudest complaints cluster around runaway token burn (roughly 1.5-3x more expensive in practice than 4.6), an “ambiguity tax” where the model no longer silently rescues vague prompts, and confidently broken output on marathon runs. Users who prompt like they are writing a spec are getting enormous leverage out of it. Users who prompt the way they used to prompt 4.6 are burning through their usage caps before lunch.

OpenAI Codex CLI is an open-source (Apache 2.0), Rust-built terminal coding agent. It has over 72,000 GitHub stars. It pairs GPT-5.4’s 272K default context window, which you can push to 1M tokens, with OS-level sandboxing. That sandbox runs on Apple Seatbelt on macOS and Landlock plus seccomp on Linux. Here is the key point: Codex CLI is the only major AI coding agent that enforces security at the kernel level, not through application-layer hooks. With codex exec for CI pipelines, MCP client and server support, and a GitHub Action for PR review, it is the most infrastructure-ready rival to Claude Code in 2026.

Qwen3.6-35B-A3B is Alibaba Cloud’s Apache 2.0 sparse Mixture-of-Experts model released April 14, 2026. It carries 35 billion total parameters but activates only about 3 billion per token, and on agentic coding suites it beats Gemma 4-31B and matches Claude Sonnet 4.5 on most vision tasks. A 20.9GB Q4 quantization runs on a MacBook Pro M5, which is the reason this release has taken over half the AI timeline for the past week.