Skip to content

Examples ​

Ready-to-copy configuration lives in the repo's examples/ folder. Most of it is generated for you by npx fixlock init and npx fixlock setup; the files are there to read, review or adapt by hand.

AI assistants ​

AssistantExampleGoes to
Claude Code.mcp.json, settings.json.mcp.json, .claude/settings.json
Cursormcp.json.cursor/mcp.json
GitHub Copilotmcp.json.vscode/mcp.json
OpenAI Codexconfig.toml~/.codex/config.toml
Gemini CLIsettings.json.gemini/settings.json

The MCP entry is the same everywhere:

json
{ "mcpServers": { "fixlock": { "command": "npx", "args": ["--no-install", "fixlock", "mcp"] } } }

CI ​

GitHub ActionsBlocks the PR, reads approvals, posts a comment, re-runs when someone approves
JenkinsMultibranch pipeline stage
GitLabMerge request job

Git hook managers ​

Huskypre-commit warning and post-commit auto-lock
LefthookSame, for lefthook.yml

A complete working setup ​

npx @abinandhmj/fixlock demo --keep builds a small repo with fixlock fully set up (team, locks, rules files, Claude Code hook, MCP config) and keeps it, so you can inspect every file.

MIT licensed · A product of Algotricz