skills/commit-push/SKILL.md
Commits all current changes and pushes to remote origin on the current branch. Use when user asks to "commit and push", "commit push", or "push my changes". Do NOT use for committing without pushing or for PR creation.
npx skillsauth add armandli/get-skilled commit-pushInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Commit all current changes and push to the remote origin on the current branch.
Work through these steps sequentially. Stop early if there are no changes.
Run these commands in parallel:
git status (never use -uall)git diff to see unstaged changesgit diff --staged to see already-staged changesIf there are no changes (no untracked files, no modifications, no staged changes), report "No changes to commit." and stop.
Record this skill's usage now (before staging) so the stats file is included in the commit:
python3 ${PWD}/.claude/skills/skill-stat/scripts/record-stat.py "commit-push"
Run git add -A to stage everything.
Run these commands in parallel:
git diff --cached to see the full staged diffgit log --oneline -10 to see recent commit styleAnalyze the staged diff and draft a concise commit message (1-2 sentences) that:
Create the commit using a HEREDOC to ensure correct formatting:
git commit -m "$(cat <<'EOF'
<commit message here>
Co-Authored-By: Claude Opus 4.6 <[email protected]>
EOF
)"
If the commit fails due to a pre-commit hook, fix the issue, re-stage with git add -A, and create a new commit (never amend).
Get the current branch name:
git branch --show-current
Then push to remote:
git push origin <branch>
If the branch has no upstream, use git push -u origin <branch> instead.
Show the user:
git log --oneline -1)tools
--- name: update-readme description: Updates a project README.md with build instructions, unit test instructions, and a mermaid architecture diagram. Use when a project README needs to be created or refreshed. Trigger phrases: "update readme", "generate readme", "create readme", "refresh readme docs". Emphasizes project interfaces, extension points, and customization hooks in the diagram — not concrete implementations. Do NOT use for documentation sites, wikis, or non-project READMEs. argument-h
business
--- name: skill-stat description: Records skill usage statistics and issue reports into .claude/skill-stats.md. Increments the Uses count for a skill name, and optionally logs an issue report that increments the Issues count and appends a row to the Issue Reports table. Use when tracking how often a skill is invoked, when a user reports a problem with a skill, or when another skill needs to log its own usage. Trigger phrases: "record skill stat", "log skill usage", "report skill issue". Do NOT u
testing
--- name: revert description: Reverts ALL git changes in the working directory: staged changes, unstaged modifications, and new untracked files. Use when user asks to "revert all changes", "undo all changes", "discard all changes", "reset all git changes", or "clean working directory". Do NOT use for reverting a specific file or a specific commit — those need targeted git commands. disable-model-invocation: true --- Revert all git changes in the working directory. This is destructive and cannot
tools
Scans a Python codebase for duplicate or near-duplicate logic patterns across functions, classes, and files, then extracts those patterns into typed utility classes in a shared module. Use when the user asks to "refactor this Python code", "find duplicate logic", "extract shared utilities", "apply DRY to Python", "deduplicate Python code", or "find repeated patterns in Python". Groups extracted helpers by the object type they operate on (strings, numbers, dates, collections, etc.). Do NOT use for performance optimization (use optimize-python), for debugging logic errors, or for explaining code. Do NOT extract code that appears only once. Run this skill before optimize-python.