poitch/commit-and-push
.claude/skills/commit-and-push/SKILL.md
Stage all changes, commit with an auto-generated message, and push to the remote.
tools
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add poitch/Ciel commit-and-pushInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 5:54 PM24.4s1 file scanned
SKILL.md
- name:
- commit-and-push
- description:
- Stage all changes, commit with an auto-generated message, and push to the remote.
- disable-model-invocation:
- true
- argument-hint:
- [commit message, optional - auto-generates from diff]
- allowed-tools:
- Bash(git *), Bash(ufmt *)
Commit and Push
Stage all current changes, create a commit, and push to the remote branch.
Step 1: Check for changes
git status
If there are no staged or unstaged changes and no untracked files, inform the user there is nothing to commit and stop.
Step 2: Review changes
Run these in parallel to understand what will be committed:
git diff
git diff --cached
git log --oneline -5
Step 3: Format changed Python files
Get the list of modified and new Python files, then activate the venv and run ufmt format on them:
source venv/bin/activate && git diff --name-only --diff-filter=ACMR HEAD -- '*.py' | xargs -r ufmt format
If no Python files were changed, skip this step.
Step 4: Stage all changes
git add -A
Step 5: Generate commit message
If the user provided a message as $ARGUMENTS, use that exactly.
Otherwise, analyze the staged diff to write a concise commit message:
- First line: imperative summary under 72 characters (e.g. "Add memory tool validation")
- If needed, add a blank line followed by a short body explaining the "why"
- Follow the style of recent commits from Step 2
Step 6: Commit
Create the commit. Always use a HEREDOC to pass the message:
git commit -m "$(cat <<'EOF'
<commit message here>
Co-Authored-By: Claude Opus 4.6 <[email protected]>
EOF
)"
If the commit fails (e.g. pre-commit hook), inform the user and stop. Do NOT retry with --no-verify.
Step 7: Push
Push to the current branch's remote tracking branch:
git push
If there is no upstream branch yet, use:
git push -u origin HEAD
If the push fails (e.g. rejected due to remote changes), inform the user and stop. Do NOT force push.
Step 8: Confirm
Show the user:
- The commit hash and message
- Which branch was pushed and to where
Related Skills
poitch/wait-and-fix
development
VerifiedTrustedCommunity
Wait for Copilot code review to complete, then address any review comments.
SKILL.mdUpdated Apr 17, 2026
poitch/pr-comments
development
VerifiedTrustedCommunity
Pull all file comments from the current GitHub pull request and address them by making code changes.
SKILL.mdUpdated Apr 17, 2026
poitch/merge-pr
data-ai
VerifiedTrustedCommunity
Squash-merge the current PR, delete the branch, and switch back to main.
SKILL.mdUpdated Apr 17, 2026
poitch/create-pr
data-ai
VerifiedTrustedCommunity
Create a new branch from main, commit all changes, push, and open a pull request.
SKILL.mdUpdated Apr 17, 2026