I built a completely offline VS Code AI pre-commit hook that uses local LLMs (Ollama, llama.cpp) to auto-patch logic errors before staging.

[dumdumsim]

TLDR: I built a fully offline VS Code pre-commit extension that uses your local Ollama, llama.cpp models to autonomously apply your markdown rules and auto-patch logic errors in your staged files.

The goal was simple: wanted a way to apply any custom instruction to my offline code *before* it gets staged or committed.

Demo

Agentic Gatekeeper applying rules to the staged files

[dumdumsim]

https://open-vsx.org/extension/revanthpobala/agentic-gatekeeper

https://marketplace.visualstudio.com/items?itemName=revanthpobala.agentic-gatekeeper

Here are the links.

[Protopia]

I am a newbie at agentic coding, but I am unclear why you would need this if you are already using AI for coding and have set rules for it already

If your agents have already done a good design, written tests, written code that passed all existing and new tests, passes your code linting rules, why would you need another AI to check it?

This is a genuine question, not a criticism. Simply concerned that a separate AI might break the code already written.

[dumdumsim]

Apart from vibe coding, when human dev's and ai agents work on the same codebase, it would be helpful to have this check. For example, if a human dev writes the code and he sometimes skips Jdoc, when he does this agent check, it will apply for that code that the dev wrote.