skills.rest
taptap
taptapOFFICIAL
Explore all skills by this author →
Website𝕏@taptapGitHub

git-commit-push

Automate staging, committing, and pushing Git changes with branch and task ID handling.

Updated Aug 27, 2026
Search Tags:#git#commit#pipeline#push#branch#code-review#task-id
One-click install
npx skills add https://github.com/taptap/agents-plugins --skill git-commit-push-taptap
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-push
Source: https://github.com/taptap/agents-plugins/tree/main/plugins/git/skills/commit-push
Command: npx skills add https://github.com/taptap/agents-plugins --skill git-commit-push-taptap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the manual Git workflow of staging, composing compliant commits, and pushing changes by automating branch handling, task ID extraction, pre-push review, and upstream configuration to reduce errors and save developer time.

Core Features & Use Cases

  • Automates default-branch detection and creates feature branches when the user is on the default branch.
  • Extracts and normalizes task IDs from branch names or user input, enforces no-ticket policies, and generates commit messages that follow project commit format.
  • Integrates an optional pre-push code review step, performs guarded push operations (including upstream setup), and can monitor CI pipelines for associated merge requests.
  • Use case: a developer finishing a feature can run this Skill to produce a properly formatted commit tied to a task ID, run a quick review, and push the branch while avoiding unsafe push commands.

Quick Start

Ask git-commit-push to commit and push the current changes with task ID TAP-85404.

Frequently Asked Questions about git-commit-push

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

FAQPage Schema
How do I automate git commit and push with a task ID?▼

Automating git commit and push with a task ID involves extracting the ID from your branch name, generating a compliant commit message, staging changes, and pushing to a remote feature branch. This enforces commit format rules and saves developer time by reducing manual errors.

How does branch detection work when pushing git changes?▼

Branch detection checks if you are on the default branch. If so, it automatically creates a new feature branch before staging and committing changes, ensuring you never commit directly to the main codebase.

Can I run a pre-push code review before committing to a remote branch?▼

Yes, you can run an optional pre-push code review step before executing the guarded push operation. This allows you to validate changes and configure upstream tracking safely without using unsafe push commands.

Do I need glab CLI to monitor CI pipelines for GitLab merge requests?▼

You need the optional glab CLI to interact with the GitLab API for monitoring CI pipelines associated with merge requests. Local git commands handle the core staging, committing, and pushing functionality independently.

What happens if I push changes without a task ID in the branch name?▼

If no task ID is found in the branch name or user input, the system enforces no-ticket policies. You must provide a task ID to generate a properly formatted commit message tied to your project task.

Related Skills

Explore More Software Engineering Skills→
cbleckercblecker
5

syncing-branch

Sync a local Git branch with its remote using fork-aware fetch and merge.

Community
Basic
alexmaruccialexmarucci

fix-mr-pipeline

Automate discovery and resolution of failed GitLab CI pipelines for Merge Requests.

Community
Advanced
marcioaltoemarcioaltoe
14

project-workflow

Automate Bun and TypeScript pre-commit quality gates with specified commands.

Community
Intermediate
heyAyushhheyAyushh
3

commit

Stage local changes and create conventional commit messages with prefixes.

Community
Basic