push

Create conventional commits and push repository changes to a remote.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/huangeddie/dotfiles --skill push-huangeddie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/huangeddie/dotfiles/tree/main/dot_agents/exact_packages/coding/exact_skills/push
Command: npx skills add https://github.com/huangeddie/dotfiles --skill push-huangeddie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the need to manually review changes and craft commit messages when pushing updates to a repository, streamlining your release and collaboration workflow.

Core Features & Use Cases

  • Creates a commit when needed: Detects whether changes require a new commit before pushing.
  • Conventional commit messaging: Analyzes the diff and generates a conventional commit description for clearer history.
  • Push workflow automation: Helps keep branches up to date without repetitive manual steps.

Example use case: you finish a small refactor, then want to push it to your remote while ensuring your commit message follows a conventional format.

Quick Start

Tell the assistant: push my pending changes and create a conventional commit message if a new commit is required.

Frequently Asked Questions about push

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

FAQPage Schema
How do I automatically create a conventional commit and push my git changes?

This skill analyzes your working tree diff, generates a conventional commit message, and pushes the changes to your remote repository automatically.

What is a conventional commit message and when do I need it for version control?

A conventional commit message follows a standardized format to ensure a readable commit history. You need it for version control when publishing updates to a remote repository, allowing your team to easily track changes and automate release workflows.

How do I push my repository changes without manually writing commit messages?

You can push repository changes without manually writing commit messages by triggering a push automation workflow that analyzes your code diff and automatically generates a standardized conventional commit description before publishing to the remote.

Does this automation tool generate a new commit if the working tree differs from the latest commit?

Yes, this automation tool checks whether your working tree differs from the latest commit, and if changes are detected, it automatically creates a new commit with a generated conventional commit message before pushing to the remote.

Can I use this push workflow automation for my daily development updates?

Yes, you can use this push workflow automation for daily development updates where updates must be published to a remote, ensuring repetitive manual steps are eliminated and your commit history remains readable.

What are the limitations of automatically generating git commit messages?

A limitation of automatically generating git commit messages is that the automation relies solely on analyzing the working tree diff, meaning it is designed for publishing updates but may not capture complex context outside the code changes themselves.