On this page
Backend Atomic Commit
Validate Django/Optimo changes before commit, check atomicity, or create an explicitly requested commit.
Overview
Validate Django/Optimo changes before commit, check atomicity, or create an explicitly requested commit.
This skill ships inside the Backend Atomic Commit plugin and can be installed through the Claude Code marketplace or directly in Codex from its skill path.
Parent Surface
Parent docs: Backend Atomic Commit
Related wrapper commands from the parent plugin:
/backend-atomic-commit:commit/backend-atomic-commit:pre-commit/backend-atomic-commit:atomic-commit When to Use This Skill
Use this Skill in backend/Django repos (especially the Diversio monolith backend) when you want:
(formatting, imports, type hints, logging, etc.) so that it matches:
Representative prompt shapes live in references/usage-examples.md.
If you’re not in a backend repo (no manage.py, no backend-style AGENTS.md, no .pre-commit-config.yaml, no backend quality docs), this Skill should say so explicitly and fall back to a lighter “generic Python pre-commit” behavior.
- /backend-atomic-commit:pre-commit – to actively fix the current code (formatting, imports, type hints, logging, etc.) so that it matches:
- Local AGENTS.md, linked repo-local docs, and quality gates.
- .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 commit message that follows the repo-local harness without any Claude or AI signatures.
- /backend-atomic-commit:commit – to run atomic-commit, then create the commit once all gates are green (no bypassing commit-msg hooks).
Modes
This Skill behaves differently based on how it is invoked:
to repo standards and pre-commit requirements.
The command markdown sets the mode. You should detect the mode from the command description/context and adjust behavior accordingly.
- pre-commit mode – invoked via /backend-atomic-commit:pre-commit:
- Actively applies changes to make the working tree and staged files conform to repo standards and pre-commit requirements.
- Runs all relevant static checks and auto-fixers.
- Does not propose or drive a commit.
- atomic-commit mode – invoked via /backend-atomic-commit:atomic-commit:
- Runs everything from pre-commit mode.
- Enforces atomicity of staged changes.
- Requires all gates to be green.
- Proposes a commit message, but must never add AI signatures or plugin branding to the message.
- commit mode – invoked via /backend-atomic-commit:commit:
- Runs everything from atomic-commit mode.
- Creates the commit once all gates are green.
- Must still never add AI signatures or plugin branding to the message.
Core Priorities
Emulate Monty’s backend engineering and review taste, tuned for pre-commit:
constraints come first.
Always verify using date +%Y-%m-%d or Python datetime — never compute dates manually. Date calculation errors have been a recurring friction point in real sessions.
try/except blocks, hidden PII, or untyped payloads.
unrelated work.
follow linked repo-local docs and directory-scoped AGENTS.md files for per-topic truth, and do not treat CLAUDE.md as a unique rule source.
.pre-commit-config.yaml hooks as documented, not ad-hoc commands.
and structured logging over untyped dicts and log soup.
wrote them; this Skill should be invisible from git log.
Always prioritize [BLOCKING] issues over style and nits.
- Never eyeball date/time math (day-of-week, "yesterday", timezone edges). Always verify using date +%Y-%m-%d or Python datetime — never compute dates manually. Date calculation errors have been a recurring friction point in real sessions.
Validation
For any pre-commit, atomic-commit, or commit run, read validation. It owns file selection, hook-first execution, gate-cache identity, type gates, bounded fix loops, and no-publication local-ci validation. Do not repeat a passing gate for unchanged inputs.
Resources
Declared allowed tools:
BashReadEditGlobGrep References
backend-taste-and-fix-rules.mdusage-examples.mdvalidation.mdworkflow-boundary.md
Installation
Switch between Claude Code and Codex, then copy the install command for the runtime you use.
claude plugin marketplace add DiversioTeam/agent-skills-marketplace
claude plugin install backend-atomic-commit@diversiotech CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
python3 "$CODEX_HOME/skills/.system/skill-installer/scripts/install-skill-from-github.py" \
--repo DiversioTeam/agent-skills-marketplace \
--path plugins/backend-atomic-commit/skills/backend-atomic-commit Invocation:
/backend-atomic-commit:commit
/backend-atomic-commit:pre-commit
/backend-atomic-commit:atomic-commit name: backend-atomic-commit