armandli/commit-push-pr
skills/commit-push-pr/SKILL.md
Creates a new branch named after the changes, stages all current changes (including untracked files), commits them, and pushes the branch to the remote named upstream (falls back to origin if upstream does not exist). Use when user asks to "commit and push to upstream", "create a branch and push", "push to upstream", or "commit push pr". Do NOT use for committing to the current branch or for creating pull requests.
tools
Updated May 30, 2026
$ install --global
skillsauthnpx skillsauth add armandli/get-skilled commit-push-prInstall 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: May 30, 2026, 3:32 AM203.4s1 file scanned
SKILL.md
- name:
- commit-push-pr
- description:
- Creates a new branch named after the changes, stages all current changes (including untracked files), commits them, and pushes the branch to the remote named upstream (falls back to origin if upstream does not exist). Use when user asks to "commit and push to upstream", "create a branch and push", "push to upstream", or "commit push pr". Do NOT use for committing to the current branch or for creating pull requests.
- disable-model-invocation:
- true
You are executing the commit-push-pr skill. Follow these steps sequentially and precisely.
Step 1 — Check Status
Run git status and git diff in parallel.
If there are no changes (no untracked files, no modifications), output "No changes to commit." and stop immediately.
Step 1.5 — Record Usage
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-pr"
Step 2 — Stage All Changes
Run git add -A to stage all changes including untracked files.
Step 3 — Analyze Changes and Generate Names
Run git diff --cached and git log --oneline -10 in parallel.
From the staged diff, derive:
- A short branch name: 2–4 kebab-case words that describe the change (e.g.,
add-login-validation,fix-null-pointer). Must be safe for git branch names: lowercase, no spaces, no special characters except hyphens. - A commit message: 1–2 sentences focused on "why", following the style of recent commits in the log.
Step 4 — Create New Branch
Run:
git checkout -b <branch-name>
If the branch name already exists (command fails), append a short numeric suffix (e.g., -2, -3) and retry.
Step 5 — Commit
Create the commit using HEREDOC format:
git commit -m "$(cat <<'EOF'
<commit message>
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
EOF
)"
If the commit fails due to a pre-commit hook, fix the reported issue, re-stage with git add -A, and create a new commit. Never use --amend.
Step 6 — Determine Remote
Run git remote to list available remotes.
- If
upstreamappears in the list → useupstream - Otherwise → use
origin
Step 7 — Push
Run:
git push -u <remote> <branch-name>
Always use -u since this is a new branch.
Step 8 — Report
Show the user:
- The new branch name
- The commit hash and message (run
git log --oneline -1) - Which remote was used and the push result
Related Skills
armandli/skills/update-readme
tools
VerifiedTrustedCommunity
--- 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
SKILL.mdUpdated May 30, 2026
armandli/skills/skill-stat
business
VerifiedTrustedCommunity
--- 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
SKILL.mdUpdated May 30, 2026
armandli/skills/revert
testing
VerifiedTrustedCommunity
--- 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
SKILL.mdUpdated May 30, 2026
armandli/refactor-python
tools
VerifiedTrustedCommunity
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.
SKILL.mdUpdated May 30, 2026