Git Pushing
Skill ActiveStage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
Automate the process of staging, committing with conventional messages, and pushing git changes to a remote repository, streamlining developer workflows.
Features
- Automatic staging of all changes
- Conventional commit message generation
- Automated push to remote branch
- Handles custom commit messages
- Provides informative status and error messages
Use Cases
- When a user wants to commit and push changes
- When a user mentions pushing to a remote
- When completing a feature and needing to save work
- When a user requests to commit and push their work
Non-Goals
- Performing complex git rebasing or merging
- Managing multiple remotes
- Resolving merge conflicts
Workflow
- Stage all changes
- Determine commit type and scope
- Generate conventional commit message (or use provided message)
- Create git commit with Claude Code footer
- Push changes to the remote branch
- Provide status or error message
Trust
- warning:Issues AttentionThere are 6 open issues and 0 closed issues in the last 90 days, indicating slow or no maintainer response to issues.
Versioning
- warning:Release ManagementThe skill is installed via `claudeCode: mhattingpete/claude-skills-marketplace` and the repository references `main` in the install instructions, but no explicit versioning is declared in the SKILL.md frontmatter or manifests.
Install
- warning:Installation instructionThe README provides installation instructions for the marketplace plugin but does not include a specific copy-paste invocation example for the `git-pushing` skill itself.
Installation
First, add the marketplace
/plugin marketplace add mhattingpete/claude-skills-marketplace/plugin install engineering-workflow-plugin@mhattingpete-claude-skillsQuality Score
Trust Signals
Similar Extensions
Project Session Manager
100Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions
Use My Browser
100Use when work depends on the user's live browser session or visible rendered state rather than static fetches, especially for browser debugging contexts or DevTools-selected elements or requests, logged-in dashboards or CMS flows, localhost apps, forms, uploads, downloads, media inspection, DOM or iframe inspection, Shadow DOM, or browser failures that look like soft 404s, auth walls, anti-bot checks, or rate limits.
Github
100Use gh for GitHub issues, PR status, CI/logs, comments, reviews, releases, and API queries.
Acp Router
100Route plain-language requests for Pi, Claude Code, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or explicit ACP harness work into either OpenClaw ACP runtime sessions or direct acpx-driven sessions ("telephone game" flow). For coding-agent thread requests, read this skill first, then use only `sessions_spawn` for thread creation. Codex chat binding defaults to the native Codex app-server plugin unless ACP is explicit or background spawn needs ACP.
Openclaw Testing
100Choose, run, rerun, or debug OpenClaw tests, CI checks, Docker E2E lanes, release validation, and the cheapest safe verification path.
Unslop Commit
100Rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50), imperative mood. Body only when "why" isn't obvious from the subject. Use when user says "humanize commit", "de-slop commit message", "make this commit sound human", "/unslop-commit", "/commit", "write a commit", or pastes a draft commit to clean up. Auto-triggers when staging changes.