github-commit-push

Automate GitHub commit and push workflows with SSH-based remote synchronization.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/xdrshjr/JR-Agent-Skills --skill github-commit-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-commit-push
Source: https://github.com/xdrshjr/JR-Agent-Skills/tree/main/github-commit-push
Command: npx skills add https://github.com/xdrshjr/JR-Agent-Skills --skill github-commit-push

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the GitHub commit and push workflow, streamlining the process of turning local changes into a coordinated remote history with robust remote configuration, conventional commits guidance, and SSH-based pushing.

Core Features & Use Cases

  • Automatic remote configuration: sets up the repository remote when missing and aligns it with the project.
  • Conventional commits guidance: encourages standardized commit messages for readability and changelog maintenance.
  • Conflict-aware pushes: detects divergences and merges remote changes before pushing to avoid conflicts.
  • SSH push security: uses SSH keys for secure authentication and easier credential management.
  • Use Case: in multi-developer projects, ensure every change is committed, reviewed, and pushed to origin/main with conflict resolution.

Quick Start

  • Verify Git is installed: git --version
  • Initialize a local repo (or navigate to an existing one), configure remote origin, and ensure SSH keys are set up
  • Add changes, commit with a conventional message, fetch remote updates, resolve conflicts if needed, and push:
    • git add .
    • git commit -m "feat(scope): description"
    • git fetch origin
    • git pull origin main --allow-unrelated-histories --no-rebase
    • git push origin main

Frequently Asked Questions about github-commit-push

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub commit and push workflows with SSH?

Automating GitHub commit and push workflows involves setting up remote origin, committing with conventional messages, fetching remote updates to resolve conflicts, and pushing via SSH for secure authentication and easier credential management.

What is the best way to handle conflict resolution before a Git push?

Handling conflict resolution before a Git push requires fetching remote updates and pulling changes with options like --allow-unrelated-histories --no-rebase. This detects divergences and merges remote changes to avoid conflicts during the push.

Do I need SSH keys to push commits to GitHub?

Yes, you need SSH keys configured for secure authentication. Using SSH for GitHub pushes provides easier credential management compared to manual credential entry, ensuring secure automated pushes to the remote repository.

How does conventional commits guidance improve version control workflows?

Conventional commits guidance improves version control workflows by encouraging standardized commit messages like feat(scope): description. This enhances readability and simplifies changelog maintenance across multi-developer collaborative projects.

Can I use this approach for multi-developer collaborative development projects?

Yes, this approach suits multi-developer collaborative development projects requiring remote synchronization. It ensures every change is committed, reviewed, and pushed to origin/main with conflict resolution and SSH-based authentication.