Opinionated conventions for a fast, maintainable and portable Lua-based Neovim configuration.
Lints .env and .env.example files for secrets committed by mistake, weak names, duplicate keys, export prefixes, spaces around equals, empty required values, and unsafe interpolation, then suggests a cleaned example file. Use when a user asks "is this .env safe to commit?", "why won't dotenv load?", or "diff my .env.example". Includes a tested stdlib Python linter.
Reviews and rewrites Git commit messages to Conventional Commits quality — clear type/scope, imperative subject, useful body explaining why — and trains the author with concrete before/after feedback.
Back from vacation? Summarizes what changed in your repos, channels and tickets while you were away.
Answers 'why on earth is this code like this?' by digging through git history, old PRs and issues, and writes the backstory of any file or function in plain English.
Rides along with whoever is on call: when an alert fires it gathers recent deploys, related past incidents and the relevant runbook, and posts a first-look summary before the human has opened the laptop.
Watches the SDKs and libraries you depend on and explains each release in terms of YOUR code: which calls are affected, what to change, and whether it's worth upgrading now.
