commitlisted

# Commit Changes You are tasked with creating git commits for the changes made during this session. Read `~/.claude/skills/shared/bash-rules.md` for bash command constraints. ## Context - Ignore rules: !`cat .gitignore 2>/dev/null || true` - Unstage all: !`git reset HEAD 2>/dev/null || true` - Remote ahead by: !`git fetch origin --quiet 2>/dev/null || true; git rev-list --count HEAD..@{upstream} 2>/dev/null || echo "n/a"` - Uncommitted changes: !`git status --short` - Diff summary: !`git diff HEAD --stat` - Full diff: !`git diff HEAD` - Recent commits: !`git log --oneline -10` ## CRITICAL CONSTRAINT **The ONLY direct file changes this skill may make are through `/clean-code` and `/documentation`.** Never move, rename, or delete source files. Never restructure code beyond what those skills do. ## Process: **Pacing:** Steps 1–6 are preparation. Sub-skills may legitimately pause when they find substantive changes needing approval (e.g. clean-code proposing dead-code removal, documentation proposing edits). Honor those gates. But when a sub-skill finishes with nothing to report, continue immediately to the next step — do not insert an extra confirmation gate. The only gates the commit skill itself owns are step 6 (plan-filename warning, if triggered), step 7 (commit-plan approval), and step 8 (push). 1. **Assess the current state of the repository** (use Context above): - **Remote sync check (do this first):** If **Remote ahead by** is > 0, the remote has commits you d