patrick-motard/git-push
plugins/pm/skills/git-push/SKILL.md
Commit changes logically with meaningful messages and push to remote. Use when the user wants to commit and push their work, or says "push", "commit and push", "ship it", etc.
$ install --global
skillsauthnpx skillsauth add patrick-motard/claude-plugins-public git-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 24, 2026, 8:34 PM0.4s1 file scanned
SKILL.md
- name:
- git-push
- description:
- Commit changes logically with meaningful messages and push to remote. Use when the user wants to commit and push their work, or says "push", "commit and push", "ship it", etc.
Git Push
Review all changes in the current branch and commit them into one or more logical commits with meaningful commit messages.
Steps
- Run
git statusandgit diffto see all changes - Analyze the changes and group them logically (e.g., separate feature additions from documentation updates, group related changes together)
- For each logical group:
- Stage the relevant files using
git add - Create a commit with a message that explains WHAT changed and WHY
- The commit message should be clear and descriptive, not generic
- Stage the relevant files using
- After all commits are created, push to the remote repository
- Confirm the push was successful
Commit message guidelines
- Be specific about what changed
- Explain the reason or context for the change
- Use imperative mood (e.g., "Add" not "Added")
- Keep the first line concise, add details in the body if needed
Related Skills
patrick-motard/git-rewrite
testing
VerifiedTrustedCommunity
Analyze and reorganize git branch history into logical, shippable commits. Automatically identifies patterns like RuboCop fixes, test iterations, and implementation evolution, then creates clean commit history with comprehensive messages.
1SKILL.mdUpdated Apr 24, 2026
patrick-motard/extract-workflow
tools
VerifiedTrustedCommunity
Review recent work and recommend automation as a skill, command, agent, or documentation. Use when a complex workflow was just performed and could be automated for reuse.
1SKILL.mdUpdated Apr 24, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026