backend-atomic-commitlisted

# Backend Atomic Commit Skill ## When to Use This Skill Use this Skill in backend/Django repos (especially the Diversio monolith backend) when you want: - `/backend-atomic-commit:pre-commit` – to **actively fix** the current code (formatting, imports, type hints, logging, etc.) so that it matches: - Local `AGENTS.md` / `CLAUDE.md` rules. - `.pre-commit-config.yaml` expectations. - `.security/` diff helpers (ruff and local imports). - Monty’s backend taste. - `/backend-atomic-commit:atomic-commit` – to run the same checks plus: - Enforce that the **staged changes are atomic** (one coherent change). - Ensure all quality gates are green (no shortcuts). - Propose a strict, ticket-prefixed commit message **without** any Claude or AI signatures. ## Example Prompts - “Run `/backend-atomic-commit:pre-commit` on this repo and actively fix all files in `git status` so they obey backend `AGENTS.md`, `.pre-commit-config.yaml`, `.security/*` helpers, and Monty’s taste (no local imports, strong typing, structured logging). Then summarize what you changed and what’s still `[BLOCKING]`.” - “Use `/backend-atomic-commit:atomic-commit` to prepare an atomic commit for the staged changes in `backend/`. Enforce all pre-commit hooks and `.security` scripts, run Ruff, ty, Django checks, and relevant pytest subsets, then propose a ticket-prefixed commit message with **no AI signature** and clearly mark any `[BLOCKING]` issues.” - “Treat my current backend chan