Atomic Commit Skill

When to Use

Atomic workflow: validate → commit → push → PR/MR → verify. All changes committed as single unit with zero warnings policy.

For large features (3+ distinct concerns), consider the stacked-prs skill instead.

Overview

Orchestrates complete code submission as state machine with 7 phases:

1. PRE_COMMIT - Validation (quality gate, secrets scan)
2. COMMIT - Atomic commit creation (conventional format)
3. PRE_PUSH - Remote sync check
4. PUSH - Upload to origin
5. PR_CREATE - Open pull request (GitHub) or merge request (GitLab)
6. VERIFY - Wait for CI checks
7. REPORT - Success summary

Zero warnings policy: Any warning fails the workflow and triggers rollback.

Platform Detection

Auto-detect from git remote:

REMOTE=$(git remote get-url origin)
if echo "$REMOTE" | grep -qi "github"; then
  PLATFORM="github"; CLI="gh"
elif echo "$REMOTE" | grep -qi "gitlab"; then
  PLATFORM="gitlab"; CLI="glab"
fi

CLI Command Mapping

Arguments

State Machine

[Start] → PRE_COMMIT → COMMIT → PRE_PUSH → PUSH → PR_CREATE → VERIFY → REPORT → [Success]
              ↓           ↓         ↓         ↓          ↓         ↓
            [Fail]      Rollback  Rollback  Rollback   Rollback  Rollback

Quality Gates

Rust-Specific Checks

Before committing, verify:

• cargo fmt --check passes
• cargo clippy --workspace --all-targets --all-features -- -D warnings passes
• cargo nextest run --workspace passes
• No unsafe blocks without // SAFETY: comments

Commit Format

type(scope): Brief description (50 chars max)

- Why (not what) - user perspective
- Reference issues: Fixes #123

Types: feat, fix, docs, style, refactor, perf, test, ci, chore

Rationalizations

Red Flags

• Bypassing the quality gate for "trivial" changes
• Committing without running validation checks
• Disabling rollback on failure