Agent skill · software engineering · aiskillstore

backend-atomic-commit

Pedantic backend pre-commit and atomic commit Skill for Django/Optimo-style repos. Enforces local AGENTS.md / CLAUDE.md, pre-commit hooks, .security/* helpers, and Monty’s backend engineering taste – with no AI signatures in commit messages.

Why this skill is useful

Adds executable scripts for enforcing strict commit standards and automating pre-commit checks tailored to specific backend conventions.

What it needs

Requires bash installed locally. About 11k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.

What this skill does

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 changes as one logical bugfix and run /backend-atomic-commit:pre-commit in a strict mode: eliminate local imports, fix type hints (no Any, no string-based annotations), clean up debug statements, and ensure Ruff, .security/localimportsprdiff.sh, ty, and Django checks are happy." “Before I commit these optimo changes, run /backend-atomic-commit:atomic-commit --auto to: enforce structured logging with TypedDict payloads, ensure no PII in logs, verify tests and .security/ scripts, and then tell me whether the commit is ready and what the commit message should be.” If you’re not in a backend repo (no manage.py, no backend- …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills aiskillstore/backend-atomic-commit

View the source on GitHub

Browse the @skills marketplace