push

Stage vault changes, generate commit messages, and sync with the remote Git repository.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ThuHuynh1438/pm-kit --skill push-thuhuynh1438
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/ThuHuynh1438/pm-kit/tree/main/.claude/skills/push
Command: npx skills add https://github.com/ThuHuynh1438/pm-kit --skill push-thuhuynh1438

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit and push vault changes to Git with smart commit messages. Auto-stages files, creates meaningful commits, and syncs with remote. Use after making vault changes or at end of day.

Core Features & Use Cases

  • Stages all changes automatically, including new and deleted files.
  • Creates smart commit messages with optional custom text or auto-generated summaries.
  • Synchronizes with the remote repository, including rebasing before pushing and conflict handling.

Quick Start

Trigger the vault commit workflow by running /push after making 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 commits and push vault changes to a remote repository?

Automating Git commits for vault changes involves auto-staging all file modifications, generating smart commit messages, and syncing with the remote. This workflow stages new and deleted files, applies safety checks, and uses structured timestamped formats before pushing.

How do I create smart commit messages for daily notes and vault content automatically?

Smart commit messages are generated automatically for vault content like daily notes and decisions when custom text is not provided. The system creates structured summaries using a timestamped format, ensuring meaningful commit history without manual input.

Can I sync my vault with a remote Git repository and handle conflicts during the push?

Syncing a vault with a remote Git repository includes rebasing before pushing and handling conflicts. The workflow performs deterministic Git operations to safely synchronize all staged vault changes with the remote branch.

What is the best way to commit and push Obsidian vault content to Git at the end of the day?

Committing and pushing vault content at the end of the day is best handled by triggering a workflow that auto-stages all changes and syncs with the remote. This safely commits daily notes, blockers, and decisions using auto-generated messages.

Do I need to manually stage deleted vault files before committing to version control?

Manually staging deleted vault files is unnecessary because the workflow automatically stages all changes. It detects file additions, modifications, and deletions across the vault, staging them deterministically before creating the commit.

Why does my vault sync workflow require safety checks before pushing to Git?

Vault sync workflows require safety checks to ensure deterministic Git operations and prevent data loss during remote synchronization. These checks validate staged content and verify structured commit messages before executing the push.