EXP-003 · active
GitKit
// the ritual, automated
One guided flow for hooks, .gitignore, .gitattributes and git config — then saved as a build you can re-apply to any project with a single command.
Install
curl -fsSL https://get.univerlab.org/gitkit | sh irm https://get.univerlab.org/gitkit.ps1 | iex A line-ending that wouldn’t behave.
It started with a commit that changed nothing — just line endings, silently rewritten somewhere between my work Mac, my Windows box and the agents on WSL. Chasing it down led me to .gitattributes. That led to git hooks: built into git, genuinely powerful, and ignored by almost everyone — because wiring them into every repo is a chore. So I deleted the chore. That’s gitkit.
$ git commit -m "feat: parse manifests"
✓ conventional-commits (commit-msg)
✓ no-secrets (pre-commit)
[main 7f3a9c1] feat: parse manifests
$ git push
→ origin/main · push.autoSetupRemote One flow
- Built-in hooks: conventional commits, secret detection, branch naming — embedded, offline.
- Every gitignore.io template plus curated git config presets, applied idempotently.
gitkit clonebootstraps a repo the moment it lands on disk.- Builds: save a setup once, apply it to every future project.
FAQ
- How do I prevent AI agents from making bad commits?
- GitKit sets up git hooks in one flow — conventional commits, secret detection, branch naming. Hooks run offline, embedded in the repo. Agents can't push code that doesn't compile or contains secrets.
- What are GitKit "builds"?
- A build saves your git configuration (hooks, ignore, attributes, config) as a reusable template. Apply it to any future project with one command — no need to reconfigure hooks for every repo.