push

star 9

Commit staged changes and push to remote

alexanderop By alexanderop schedule Updated 1/25/2026

name: push description: Commit staged changes and push to remote allowed-tools: Bash(git status), Bash(git diff:), Bash(git log:), Bash(git add:), Bash(git commit:), Bash(git push:), Bash(git rev-parse:), Bash(git remote:*)

Commit and Push

I have gathered information about your changes. Here are the results:

!`git status` !`git diff --cached` !`git diff` !`git log --oneline -10` !`git rev-parse --abbrev-ref HEAD` !`git remote -v`

Instructions

Step 1: Commit (if there are changes)

  1. Analyze the diffs above to understand what changed.

  2. Stage files if needed (skip already staged files, skip files that shouldn't be committed like .env).

  3. Generate a conventional commit message following this format:

    <type>(<scope>): <description>
    
    [optional body]
    

    Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore

  4. Create the commit using a HEREDOC for proper formatting:

    git commit -m "$(cat <<'EOF'
    type(scope): description
    EOF
    )"
    

Step 2: Push

  1. Push to remote using the current branch:

    git push origin <current-branch>
    

    If the branch doesn't have an upstream, use:

    git push -u origin <current-branch>
    
  2. Show the result with git log -1 to confirm the commit, and verify the push succeeded.

Install via CLI
npx skills add https://github.com/alexanderop/dotfiles --skill push
Repository Details
star Stars 9
call_split Forks 0
navigation Branch main
article Path SKILL.md
More from Creator