Opinionated conventions for idempotent, testable and safe Ansible playbooks and roles.
Reviews PostgreSQL and MySQL schema migrations (raw SQL or ORM-generated) for table locks, rewrites, data loss, and breaking changes, then proposes safe zero-downtime rewrites with a clear verdict.
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.
Explains any cron expression in plain English, lists the next run times, and flags pitfalls such as the day-of-month OR day-of-week rule, dates that never occur, DST gaps, UTC versus local time, and overlapping jobs. Includes a tested stdlib Python checker for crontab files.
Reviews dependency update PRs from Dependabot or Renovate: reads the changelogs, flags breaking changes and security fixes, and tells you which ones are safe to merge in bulk.
Finds old and abandoned Git branches in your repositories, checks whether their work was merged or still matters, and asks owners before suggesting a safe cleanup list.
After an incident it collects the alert timeline, chat messages, deploys and graphs into a blameless postmortem draft with impact, root cause, and follow-up actions.
Checks your servers over SSH on a schedule: disk, memory, failing services, certificate expiry and suspicious logins, then sends a short health report and alerts only when something needs you.
