← ClaudeAtlas

commitlisted

Commit staged and unstaged changes with a clean, why-focused message. Use when the user says "commit", "save this", "commit what we did", or wants to wrap up a coding session.
TomasLicek/ai · ★ 1 · AI & Automation · score 75
Install: claude install-skill TomasLicek/ai
# Commit Create a git commit for staged/unstaged changes. ## Context from caller $ARGUMENTS ## Current git state - Status: !`git status` - Staged diff: !`git diff --staged` - Unstaged diff: !`git diff` - Recent commits: !`git log --oneline -5` ## Steps 1. Analyze the git state above — no need to re-run those commands 2. Analyze changes, draft commit message: - Use the context above to understand what was done - Focus on WHY not WHAT - 1-2 sentences max - Match repo's commit style 3. Stage and commit: - Stage specific files relevant to the change (NOT `git add -A` or `git add .`) - Skip .env, credentials, secrets, large binaries - Commit with HEREDOC: ```bash git add file1 file2 && git commit -m "$(cat <<'EOF' Your message here EOF )" ``` 4. Report: commit hash, files changed ## Rules - NEVER amend, force push, or skip hooks - NEVER commit .env, credentials, secrets - If nothing to commit, just say "Nothing to commit" - If pre-commit hook fails, report the error (don't fix)