Skills Guide

Git Push to GitHub

VerifiedCaution

Commits and pushes changes to GitHub remote repository using Conventional Commits format.

Download and use
Sby Skills Guide Bot
DevelopmentBeginner
7/24/2026
Claude CodeCursorWindsurfCodex
#git#github#conventional-commits#version-control#push

Recommended for

Backend developerClaude CodeCode reviewFrontend developerCursorFullstack developer

Automated summary

This skill inspects uncommitted changes, drafts a message in Conventional Commits format, then runs the full add, commit and push cycle to the remote GitHub repository.

Strengths

  • Runs the whole status, staging, commit and push flow end to end without manual steps
  • Infers the commit type and scope automatically from the changed files
  • Recovers from a rejected push by rebasing onto the current branch's remote before retrying
  • Supports --amend, --no-verify and a caller-supplied commit message

Limitations

  • Always appends a Co-Authored-By footer without asking for confirmation
  • Does not cover pull request creation or conflict resolution beyond the automatic rebase
  • Assumes a repo already wired to a GitHub remote with push permissions
When to use it

Use it when you want to quickly record and publish a batch of finished changes to the remote branch.

When not to use it

Avoid it when you need fine control over what gets committed, want to write the message yourself, or must not rewrite shared history.

Security analysis

Caution
Quality score84/100

The skill uses standard git commands for a legitimate commit-and-push workflow, but it executes shell/network operations and offers options that bypass hooks or rewrite commits. It does not exfiltrate secrets, run obfuscated payloads, or perform destructive filesystem actions, so it is not risky, but its powerful git operations warrant caution.

Findings
  • •No allowed-tools declared, but instructions execute git commands via shell
  • •git push publishes local changes to a remote repository
  • •--no-verify option bypasses pre-commit hooks and safety checks
  • •--amend rewrites the last commit and could cause confusion if already pushed
  • •git pull --rebase can rewrite local history and produce conflicts
How this analysis is made

Examples

Commit and push current work
Review my uncommitted changes and push them to GitHub with a proper Conventional Commits message.
Fix rejected push
My push to origin was rejected — rebase on the current branch and push my commits again.
Amend last commit
Add the staged fix to my last commit with --amend and push it to the remote.

name: git-push description: Commits and pushes changes to GitHub remote repository using Conventional Commits format. metadata: tags: [Git, GitHub, Push, Development, Workflow]

Git Push

Commit uncommitted changes and push to remote GitHub repository. Handles the complete flow: stage, commit, and push.

Instructions

  1. Check Git Status

    • Run git status
    • Show all uncommitted changes

  2. Analyze Changes

    • Review changed files
    • Determine commit type (feat/fix/docs/refactor/test/chore)
    • Determine scope (affected module/component)

  3. Create Commit Message Follow Conventional Commits format:

    <type>(<scope>): <subject>

<body>

<footer>

    Types:

    • feat: New feature
    • fix: Bug fix
    • docs: Documentation update
    • refactor: Code refactoring
    • perf: Performance optimization
    • test: Test related
    • chore: Other changes

  4. Stage and Commit

    • Run git add for affected files
    • Create commit with formatted message
    • Include Co-Authored-By: Claude <noreply@anthropic.com> in footer

  5. Push to Remote

    • Run git push
    • If rejected, pull with rebase first: 
      git pull --rebase origin $(git branch --show-current)
git push

  6. Verify Success

    • Show commit SHA
    • Show remote branch status

Options

  • --amend - Amend last commit instead of creating new one
  • --no-verify - Skip pre-commit hooks
  • Custom commit message can be provided directly in <type>(<scope>): <message> format

Integration

This skill uses the same Conventional Commits format as git-commit but focuses on the complete flow: stage, commit, and push.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/git-push-to-github-mryiqh66/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/git-push-to-github-mryiqh66' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-push-to-github-mryiqh66/download' --output '.skill-downloads/git-push-to-github-mryiqh66/SKILL.md.part' && mv '.skill-downloads/git-push-to-github-mryiqh66/SKILL.md.part' '.skill-downloads/git-push-to-github-mryiqh66/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/git-push-to-github-mryiqh66/SKILL.md' && test -s '.skill-downloads/git-push-to-github-mryiqh66/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/git-push' && cp -R '.skill-downloads/git-push-to-github-mryiqh66' '.claude/skills/git-push'

Cursor
test -f '.skill-downloads/git-push-to-github-mryiqh66/SKILL.md' && test -s '.skill-downloads/git-push-to-github-mryiqh66/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/git-push' && cp -R '.skill-downloads/git-push-to-github-mryiqh66' '.cursor/skills/git-push'

Codex
test -f '.skill-downloads/git-push-to-github-mryiqh66/SKILL.md' && test -s '.skill-downloads/git-push-to-github-mryiqh66/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/git-push' && cp -R '.skill-downloads/git-push-to-github-mryiqh66' '.agents/skills/git-push'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/git-push-to-github-mryiqh66'

openskills read 'git-push-to-github-mryiqh66'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/git-push-to-github-mryiqh66/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot