git-helper

Automate git staging, commits, pushes, pulls, and pull requests.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/sih3rron/skills --skill git-helper-sih3rron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-helper
Source: https://github.com/sih3rron/skills/tree/main/git-helper
Command: npx skills add https://github.com/sih3rron/skills --skill git-helper-sih3rron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The git-helper skill removes friction from common git workflows by allowing users to perform staging, generate concise conventional commit messages from staged diffs, commit, push, pull, and create GitHub pull requests using natural-language commands while enforcing safety checks.

Core Features & Use Cases

  • Auto-generated commits: Inspect staged diffs and produce a conventional commit message with inferred type and scope, ask for confirmation on large or mixed changes, and commit on approval.
  • Staging assistance: Stage specific files, globs, or everything, and interactively resolve ambiguous staging requests by showing git status.
  • Push and pull management: Push with upstream setup when missing, show remote and branch details, warn on protected branches, and suggest stashing before pulling if there are uncommitted local changes.
  • GitHub PR creation: Summarize commits, infer a PR title and body, and create PRs via the gh CLI with a sensible default base branch and authentication checks.
  • Guardrails: Prevent accidental direct commits to main/master, avoid force-pushes without explicit confirmation, and require gh authentication for PR operations.

Quick Start

Use the git-helper to stage all unstaged changes, generate a conventional commit message from the staged diff, commit, and push to the current branch.

Frequently Asked Questions about git-helper

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

FAQPage Schema
How do I generate conventional commit messages from staged git diffs automatically?

To generate conventional commit messages automatically, the git-helper inspects your staged diffs and infers the commit type and scope. It asks for confirmation on large or mixed changes before committing the staged files.

Can I create a GitHub pull request from the command line without manually writing a title and body?

You can create GitHub pull requests using natural-language commands via the gh CLI. The git-helper summarizes your commits, infers a sensible PR title and body, selects a default base branch, and verifies gh authentication before creating the PR.

How do I prevent accidental direct commits or force-pushes to protected branches like main?

To prevent accidental direct commits to main or master, the git-helper enforces built-in guardrails that block direct commits to protected branches. It also requires explicit confirmation before executing any force-push operations.

What is the best way to handle git staging when I have ambiguous or mixed unstaged changes?

To handle ambiguous staging requests, the git-helper resolves uncertainty by showing the current git status. You can stage specific files, use glob patterns, or stage everything interactively before generating a commit message.

How do I push to a remote branch that doesn't have an upstream set yet?

To push to a remote branch missing an upstream, the git-helper automatically sets up the upstream tracking configuration. It shows remote and branch details, warns if targeting protected branches, and suggests stashing before pulling if you have uncommitted local changes.