home / skills / jst-well-dan / skill-box / git-pushing

git-pushing skill

safe

This skill stages, commits, and pushes changes using conventional commits via a scripted workflow to share work remotely.

This is most likely a fork of the git-pushing skill from openclaw

npx playbooks add skill jst-well-dan/skill-box --skill git-pushing

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

1.1 KB

---
name: git-pushing
description: 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.
author: ComposioHQ
---

# 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
bash skills/git-pushing/scripts/smart_commit.sh
```

With custom message:
```bash
bash skills/git-pushing/scripts/smart_commit.sh "feat: add feature"
```

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

Overview

This skill stages, commits, and pushes Git changes using a consistent, conventional-commit format. It automates the full push workflow so you don’t have to run manual git commands. Use it when you want a reliable, repeatable commit + push that includes conventional messaging and remote linking.

How this skill works

The skill runs a dedicated script that stages all changes, constructs a conventional commit message (or accepts a custom message), attaches a footer for traceability, and pushes to the current remote branch with the upstream flag. You always invoke the script rather than performing manual git steps to ensure consistent metadata and behavior across commits. A custom commit message can be supplied as an argument when needed.

When to use it

You explicitly ask to push or save work (e.g., “push changes”, “commit and push”).
You finished a feature or fix and want to publish it to the remote branch.
You mention pushing to GitHub, GitLab, or another remote.
You want consistent conventional commit messages and automated push behavior.
You prefer an automated script to handle staging, commit formatting, and push.

Best practices

Provide a concise conventional commit message when the change intent is specific (e.g., feat:, fix:, chore:).
Run the script from the repository root so it stages the intended working-tree changes.
Preview changes and run tests locally before invoking the push to avoid pushing broken code.
Use the custom message argument for nonstandard or detailed commits instead of relying on defaults.
Ensure your local branch tracks the correct remote branch to avoid push conflicts.

Example use cases

You’ve completed a bug fix and say “commit and push” — script stages, commits with fix:, and pushes.
You want to publish a new feature; call the script with a custom message like "feat: add X".
You’ve updated documentation and need a quick chore: commit and push with consistent metadata.
You’re collaborating and want every push to include a traceable footer and conventional formatting.

FAQ

Can I provide my own commit message?

Yes — pass the message as an argument to the script to override the default conventional message.

Does the script push to the correct remote branch?

The script uses git push with the upstream flag so it sets and pushes to the current branch’s remote tracking branch.