atomic-push

Automate atomic commits and pushes from working tree changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically turn the current working tree's changes into a sequence of small, well-scoped commits on the current branch, then push them to the remote.

Core Features & Use Cases

  • Atomic commits: Split changes into logical units (feature/fix/refactor/docs) and commit each unit separately.
  • Consistent messaging: Use the repository's existing commit style for all messages.
  • Push safety: Push only after all atomic commits are created; set upstream if needed.

Quick Start

Group changes into logical units, stage each unit's files, commit with the repo's existing convention, then push.

Frequently Asked Questions about atomic-push

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

FAQPage Schema
How do I split working tree changes into atomic commits and push them?

You can split working tree changes into atomic commits by grouping changes into logical units, staging each unit's files separately, committing with the repo's existing convention, and then pushing to the remote.

What is the best way to automate git workflow commits for separate logical units?

The best way to automate git workflow commits for separate logical units is to enforce required staging per unit and apply consistent commit-message conventions before pushing all changes to the remote.

Does this atomic push automation create a pull request on the remote?

No, this atomic push automation does not create a pull request. It focuses on creating separate commits on the current branch and pushing them directly to the remote, setting upstream if needed.

Can I push multiple atomic commits to a remote branch without setting upstream first?

Yes, you can push multiple atomic commits without setting upstream first. The automation handles upstream push behavior gracefully, configuring the upstream tracking branch if needed during the push.

Why does my git push fail after splitting changes into atomic commits?

A git push after splitting changes into atomic commits may fail if upstream is not set, but this automation handles that edge case gracefully by configuring the upstream tracking branch before pushing.