organized-commitslisted

Use when the user asks to organize commits, split or group by intent, write conventional messages, clean up Git history, consolidate branches or worktrees, salvage stale work, or runs $organized-commits / /organized-commits (often then push). Also apply on freeform "git commit push" when they want intent-based commits rather than one dump commit. Commit on a feature-related branch, not main/default by default. Never delete remote branches unless explicitly asked. If they want full verify + handoff + no leftovers after push, also apply finish-and-ship.
YosefHayim/dufflebag · ★ 0 · Code & Development · score 69

Install: claude install-skill YosefHayim/dufflebag

# Organized Commits Make Git history a debug timeline: one intent per commit, useful messages, and no stranded work. Run only on an explicit commit, push, ship, or consolidation request. ## Safety - Read repository instructions and inspect status, branch, upstream, recent history, staged/unstaged diffs, untracked files, worktrees, and stashes before staging. - Preserve user-owned and unrelated changes. Stop if secrets, credentials, unexplained generated files, or ambiguous overlapping intent appear. - **Feature branch by default:** if HEAD is the default branch and the work is product change (feature, fix, refactor, refinement, chore), **create/switch to a topic branch** before committing unless the user explicitly wants default-branch-only commits. - Never change Git configuration, rewrite published history, force-push a protected branch, or delete branches, tags, stashes, or worktrees without explicit authorization. - **Never `git push --delete` / delete remote refs** unless the user explicitly asks. Prefer leaving remotes for handoff and CI. - Push only when requested. Existing approval remains valid when the user already asked for commit and push in the same task. - Use merge, not rebase, to consolidate shared work. Create backup refs before integration. ## Workflow 1. Confirm branch: not accidental default-branch product commits. Branch name should reflect intent (`feat/…`, `fix/…`, `refactor/…`, …) when creating one. 2. Classify every changed path by intent: featur