Lock what's fixed
Every fix and feature commit locks its own lines, with an owner and the reason it exists. Past fixes in your history can be locked in one command.
Stop AI coding assistants (and teammates) from silently undoing bug fixes. Works with Claude Code, Cursor, GitHub Copilot and Codex. A product of Algotricz.
You fix a bug. Weeks later an AI assistant ports a feature from an old codebase, rewrites the file, and your fix is gone. Git merges it with no conflict, because to git it's a normal edit. Tests only catch it if someone wrote a test for that exact bug; code review only catches it if the reviewer remembers.
fixlock remembers for the whole team, and tells the AI before it makes the change.
npx @abinandhmj/fixlock demo # run that yourself, in a throwaway repo
pipx run fixlock demo # same, without Node.jsInstall it with npm i -D @abinandhmj/fixlock, or pipx install fixlock for a standalone binary with no Node.js needed.
| See it in action | The 60-second demo, step by step |
| How it works | The five checkpoints, and what each one catches |
| Getting started | fixlock running on your repo in 10 minutes |
| AI assistants | Connect Claude Code, Cursor, Copilot or Codex |
| Recipes | Common situations and what to do |
| FAQ | "Why not just tests?" and other questions |
| Guide | Read it if you… |
|---|---|
| Team lead guide | set up the project, the team and the rules |
| Developer guide | write code day to day and want to know what the warnings mean |
| AI tools | want the rules file for any of 12 assistants |
| CI setup | wire the PR check into GitHub Actions, Jenkins or GitLab |
| Examples | want ready-to-copy configs |
| Issue trackers | want Linear, ClickUp, Notion or Bugasura to update themselves |
| Configuration · Commands · Troubleshooting · Security | need a reference |