push

Stage changes, generate conventional commit messages, and push to Git.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/cristoslc/tidegate --skill push-cristoslc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/cristoslc/tidegate/tree/main/.agents/skills/push
Command: npx skills add https://github.com/cristoslc/tidegate --skill push-cristoslc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of staging, committing, and pushing code changes to a Git repository, including generating descriptive commit messages and handling merge conflicts.

Core Features & Use Cases

  • Automated Git Workflow: Stages changes, creates commits with AI-generated messages, and pushes to the remote repository.
  • Intelligent Commit Messages: Generates conventional commit messages based on the staged diff, including a summary and Co-Authored-By trailer.
  • Conflict Resolution: Non-interactively resolves merge conflicts by prioritizing local changes for project files and upstream for scaffolding.

Quick Start

Use the push skill to commit and push your current changes.

Frequently Asked Questions about push

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

FAQPage Schema
How do I automate git commit and push with AI-generated messages?

Automating git commit and push involves staging changes, generating descriptive conventional commit messages from the diff using AI, and pushing to the remote repository. This Skill handles the entire workflow non-interactively.

How does AI generate conventional commit messages from a git diff?

AI-generated commit messages are created by analyzing the staged git diff to produce a descriptive summary. The output adheres to conventional commit standards and automatically includes a Co-Authored-By trailer.

Can I automatically resolve merge conflicts when pushing local changes?

Automatic merge conflict resolution is handled non-interactively by prioritizing local changes for project files while keeping upstream changes for scaffolding. This ensures your local modifications are preserved during the push workflow.

Do I need the Git CLI to automate staging and pushing code changes?

Yes, the Git CLI is required to automate staging and pushing code changes. The Skill relies on Git command-line integration to execute version control operations and generate commit messages.

What is the best way to handle version control integration for automated commits?

The best way to handle version control integration for automated commits is using a workflow that stages diffs, generates conventional commit messages via AI, and pushes to the remote repository while resolving any merge conflicts.

Are there limitations to non-interactive merge conflict resolution during an automated git push?

Non-interactive merge conflict resolution applies a fixed strategy: prioritizing local changes for project files and upstream changes for scaffolding. It may not suit cases requiring custom manual conflict review before pushing.