push

Commit staged Git changes with Conventional Commits and push to remote.

3|Updated Jan 19, 2013
One-click install
npx skills add https://github.com/shifumin/dotfiles --skill push-shifumin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/shifumin/dotfiles/tree/main/dot_claude/skills/push
Command: npx skills add https://github.com/shifumin/dotfiles --skill push-shifumin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of committing staged changes to a Git repository and pushing them to a remote origin, streamlining the development workflow.

Core Features & Use Cases

  • Automated Git Operations: Stages changes, creates commits with Conventional Commits format, and pushes to the remote repository.
  • Pre-commit Checks: Includes checks for linters and tests to ensure code quality before committing.
  • Conflict Resolution Guidance: Provides steps for handling common Git errors like rejected pushes.
  • Use Case: After making several code modifications, you can use this Skill to quickly commit and push your work without manually typing Git commands.

Quick Start

Commit and push the current changes to the remote repository.

Frequently Asked Questions about push

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

FAQPage Schema
How do I automate committing and pushing staged Git changes to a remote repository?

Automating a git commit and push requires a workflow tool that stages changes, generates a commit message, and pushes to the remote origin automatically. This Skill executes that exact sequence to streamline your development workflow.

How does Conventional Commits format work for automated Git commit messages?

Conventional Commits standardizes commit messages using structured prefixes like feat or fix. This Skill supports Conventional Commits natively, ensuring your automated git commit messages follow consistent formatting for version control tracking.

Can I run linters and tests before pushing code to a remote Git repository?

Yes, running pre-commit checks for linters and tests before pushing code is supported. This Skill includes integrated pre-commit validation to ensure code quality checks pass before executing the git commit and push operations.

What is the best way to handle rejected pushes during a Git remote sync?

Handling rejected pushes involves pulling remote changes and rebasing your local branch. This Skill guides you through pull and rebase operations to resolve common Git errors when a push is rejected by the remote repository.

What should I do if my Git push is rejected due to remote changes?

If a Git push is rejected due to remote changes, you must pull and rebase your local commits. This Skill handles common Git errors by guiding users through the necessary pull and rebase operations to sync repositories.