Git Push Workflow skill

Stage, commit, and push git changes with conventional commit messages.

by mhattingpete·Apache-2.0 license·★ 679 Stars on the repo·GitHub ↗

Use now

Files of Git Push Workflow

mhattingpete/main1 file shown
SKILL.md
Show the full text32 lines
git-pushing/SKILL.md32 lines · 1.1 KB

Git Push Workflow

Stage all changes, create a conventional commit, and push to the remote branch.

When to Use

Automatically activate when the user:

  • Explicitly asks to push changes ("push this", "commit and push")
  • Mentions saving work to remote ("save to github", "push to remote")
  • Completes a feature and wants to share it
  • Says phrases like "let's push this up" or "commit these changes"

Workflow

ALWAYS use the script - do NOT use manual git commands:

bash skills/git-pushing/scripts/smart_commit.sh

With custom message:

bash skills/git-pushing/scripts/smart_commit.sh "feat: add feature"

Script handles: staging, conventional commit message, Claude footer, push with -u flag.

1---
2name: git-pushing
3description: Stage, 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.
4---
5 
6# Git Push Workflow
7 
8Stage all changes, create a conventional commit, and push to the remote branch.
9 
10## When to Use
11 
12Automatically activate when the user:
13- Explicitly asks to push changes ("push this", "commit and push")
14- Mentions saving work to remote ("save to github", "push to remote")
15- Completes a feature and wants to share it
16- Says phrases like "let's push this up" or "commit these changes"
17 
18## Workflow
19 
20**ALWAYS use the script** - do NOT use manual git commands:
21 
22```bash
23bash skills/git-pushing/scripts/smart_commit.sh
24```
25 
26With custom message:
27```bash
28bash skills/git-pushing/scripts/smart_commit.sh "feat: add feature"
29```
30 
31Script handles: staging, conventional commit message, Claude footer, push with -u flag.
32 

Discussion

Alternatives

CI/CD and AutomationAutomates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.Infrastructure & ops · MITVersion Bump & Release WorkflowAutomated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer raised npm security.Infrastructure & ops · Apache-2.0Orca CLIOperate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser through the `orca` CLI. Use when the user says "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "handoff" / "handover" / "give this to another agent", "Orca browser", "orca artifacts", or "share skills". Prefer it over raw git worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use Computer Use only when a visible window needs GUI control that a CLI, filesystem, or API cannot do.Infrastructure & ops · MITOrca OrchestrationCoordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator loops, and decomposing work across agents. Use `orca-cli` for full ownership handoffs — "hand off", "handoff", "handover", "give this to another agent", "another worktree" — unless asked to supervise, monitor, or coordinate a DAG, and for terminal control, lightweight terminal prompts, shell commands, Orca worktree management, and reading or waiting on terminals.Infrastructure & ops · MIT