push

Stage all changes, commit with repository conventions, and push to the remote.

1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/chrisliu298/dotfiles --skill push-chrisliu298
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/chrisliu298/dotfiles/tree/main/agents/extensions/skills/push
Command: npx skills add https://github.com/chrisliu298/dotfiles --skill push-chrisliu298

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline git workflows by automating a single, cohesive commit and push to the remote.

Core Features & Use Cases

  • Single-commit workflow: Stages all changes, commits them in one message according to the repository's conventions, and pushes to the remote.
  • No PRs by default: Enforces a direct push without creating pull requests, suitable for rapid local updates.
  • Use Case: When you need to quickly capture a set of changes (e.g., bugfix + small refactor) in a single, inspectable commit.

Quick Start

Instruct the agent to stage changes, craft a commit message following the repo's conventions, and push to the remote.

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 for local changes in a single step?▼

To automate a git commit and push in a single step, you can use a workflow that stages all changes, crafts a commit message matching repo conventions, and pushes to the remote with upstream handling.

What is the best way to commit and push multiple local updates as one cohesive git commit?▼

The best way to push multiple updates as one cohesive git commit is to stage all changes together and apply a single commit message, avoiding multiple fragmented commits for rapid local updates.

Does this automated git push workflow create pull requests?▼

No, this automated git push workflow does not create pull requests by default. It enforces a direct push to the remote repository, making it suitable for rapid local updates.

How do I ensure my automated commit message follows existing repository conventions?▼

To ensure your automated commit message follows repository conventions, the workflow analyzes the repo's existing commit style and applies a matching message format when staging and committing changes.

What happens if there are no changes to commit or the git push fails?▼

If there are no changes to commit or the git push fails, the automated workflow aborts the operation to prevent errors, ensuring no-ops and push failures do not corrupt the version control state.

Can I use this single-commit workflow for both bug fixes and feature development?▼

Yes, you can use this single-commit workflow for both bug fixes and feature development. It applies to local Git workflows where capturing a set of changes in one inspectable commit is preferred.