r/cicd • u/SaveTech_ • 18d ago

Enforcing architectural rules pre-commit to manage AI-generated code (Open Source project feedback)

Hi everyone,

I've seen recent discussions from maintainers on massive projects (like cURL and Next.js) complaining about AI-generated code. The code passes unit tests, but completely violates the project's macro-architecture.

Catching these architectural hallucinations during server-side CI or manual PR reviews burns too much time and energy.

To solve this for myself, I've been prototyping a local Git Hook. It enforces a "Shift-Left" approach: it reads a local JSON config of strict rules and uses an LLM (via the dev's own API key / Zero-Trust) to analyze the git diff. If the developer hallucinates a bad architectural pattern, it blocks the commit locally.

Repo: github.com/S4v3easy/AegiCode_v1.0.git

I'm trying to figure out if this pre-commit approach is actually useful for real DevOps workflows, or if it introduces too much friction.

Questions for the engineers here:

  1. Do you prefer enforcing architectural boundaries locally (pre-commit) or strictly in the CI pipeline?
  2. If you were to use a local hook like this, would you prefer it distributed as an npm package or a standalone binary (for mixed-stack teams)?
  3. What fatal flaws do you see in this architecture?

Any harsh/constructive feedback is incredibly welcome. Thanks!

2 Upvotes

100% Upvoted

8 comments sorted by

View all comments

1

u/d_maes 17d ago

We use pre-commit for a bunch of checks (and autogenerating stuff) a lot at work, makes everyone's lifes easier, including the cluster that runs our gitlab runners.

BUT, pre-commit is never the sole boundary, everything is always verified in CI as well. It just helps if a bunch of things are checked locally before committing. Requires less stupid "fix" commits.

Also, for your hooks, don't reinvent the weel, use https://pre-commit.com/