git-session-atomic-commits

# Git Atomic Commits for Current Session ## Inherited Skills Load and delegate to these; do not re-implement their rules here: - **git-atomic-commit** — atomic partitioning, staging, commit execution, type/scope format - **git-commit-scope-constitution** — scope inventory and validation ## Workflow 1. Resolve scope: use argument text → infer from conversation + git status → ask if still ambiguous. 2. Run `git status` and `git diff`. Map each changed file/hunk to session scope or mark as unrelated. 3. If a file could belong to multiple atomic units, pause and ask before proceeding. 4. Delegate scoped changes to **git-atomic-commit** for partitioning and commit execution. 5. Validate all scopes via **git-commit-scope-constitution**. 6. Report results (see Output below). ## Safety Rules - Never stage or commit unrelated files or hunks. - Never amend existing commits unless explicitly requested. - Prefer non-destructive git commands. - Stop and report if session boundaries cannot be established confidently. ## Output Return in order: 1. Session scope identified. 2. Commits created (type/scope/message). 3. Files included per commit. 4. Unrelated changes intentionally left untouched. 5. Any ambiguities and how they were resolved.