/push
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.
$ npx -y skills add ballred/obsidian-claude-pkm --skill push --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/push
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
push.SKILL.mdname: push
description: 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.
allowed-tools: Bash, Read, Glob
model: sonnet
disable-model-invocation: true
user-invocable: true
Git Push Skill
Automates Git workflow to save your notes with meaningful commit messages and push to remote repository.
Usage
Invoke with `/push` or ask Claude to save/commit your changes.
Basic Usage
/push
With Custom Message
/push "Completed project planning"
What This Skill Does
1. **Stages All Changes**
- Adds all modified files
- Includes new files
- Removes deleted files
2. **Creates Smart Commit Message**
- Uses provided message, or
- Auto-generates from changes
- Includes date/time stamp
- Summarizes key modifications
3. **Syncs with Remote**
- Pulls latest changes (if enabled)
- Pushes to remote repository
- Handles merge conflicts gracefully
Commit Message Format
Automatic Messages
Based on your changes:
Daily note for 2024-01-15 + 3 project updates
- Added: Daily Notes/2024-01-15.md
- Modified: Projects/Learning Spanish/notes.md
- Modified: Goals/2. Monthly Goals.md
With Timestamp
[2024-01-15 09:30] Completed weekly review
Workflow Integration
Morning Routine
/daily # Create daily note
# ... work on notes ...
/push "Morning planning complete"
End of Day
# Complete daily reflection
/push # Auto-message with summary
After Weekly Review
/weekly # Run weekly review
/push "Weekly review - Week 3"
Git Operations
Standard Flow
1. `git add .` - Stage all changes 2. `git commit -m "message"` - Create commit 3. `git pull --rebase origin main` - Get remote changes 4. `git push origin main` - Push to remote
Safety Checks
- Verify Git repository exists
- Check for uncommitted changes
- Ensure remote is configured
- Validate branch exists
Conflict Handling
If conflicts occur: 1. Auto-resolve attempts (favor local for notes) 2. If manual resolution needed, guide through process 3. Never force push without explicit request
Security Considerations
Never Commit
- Passwords or credentials
- API keys
- Personal identification
- Financial information
Use .gitignore for
private/
credentials.md
.env
.obsidian/workspace*
.obsidian/cache
.trash/
.DS_Store
Troubleshooting
Push Rejected?
Pull first, then push again:
git pull --rebase origin main
git push origin main
Not a Git Repository?
git init
git remote add origin [URL]
Large Files Issue?
Consider Git LFS for images/attachments.
Integration
Works with:
- `/daily` - Commit after creating daily note
- `/weekly` - Commit after weekly review
- `/onboard` - No git needed for context loading
- Auto-commit hook for automatic saves
Read more
name: push description: 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. allowed-tools: Bash, Read, Glob model: sonnet disable-model-invocation: true user-invocable: true
Git Push Skill
Automates Git workflow to save your notes with meaningful commit messages and push to remote repository.
Usage
Invoke with `/push` or ask Claude to save/commit your changes.
Basic Usage
/push
With Custom Message
/push "Completed project planning"
What This Skill Does
1. **Stages All Changes**
- Adds all modified files
- Includes new files
- Removes deleted files
2. **Creates Smart Commit Message**
- Uses provided message, or
- Auto-generates from changes
- Includes date/time stamp
- Summarizes key modifications
3. **Syncs with Remote**
- Pulls latest changes (if enabled)
- Pushes to remote repository
- Handles merge conflicts gracefully
Commit Message Format
Automatic Messages
Based on your changes:
Daily note for 2024-01-15 + 3 project updates - Added: Daily Notes/2024-01-15.md - Modified: Projects/Learning Spanish/notes.md - Modified: Goals/2. Monthly Goals.md
With Timestamp
[2024-01-15 09:30] Completed weekly review
Workflow Integration
Morning Routine
/daily # Create daily note # ... work on notes ... /push "Morning planning complete"
End of Day
# Complete daily reflection /push # Auto-message with summary
After Weekly Review
/weekly # Run weekly review /push "Weekly review - Week 3"
Git Operations
Standard Flow
1. `git add .` - Stage all changes 2. `git commit -m "message"` - Create commit 3. `git pull --rebase origin main` - Get remote changes 4. `git push origin main` - Push to remote
Safety Checks
- Verify Git repository exists
- Check for uncommitted changes
- Ensure remote is configured
- Validate branch exists
Conflict Handling
If conflicts occur: 1. Auto-resolve attempts (favor local for notes) 2. If manual resolution needed, guide through process 3. Never force push without explicit request
Security Considerations
Never Commit
- Passwords or credentials
- API keys
- Personal identification
- Financial information
Use .gitignore for
private/ credentials.md .env .obsidian/workspace* .obsidian/cache .trash/ .DS_Store
Troubleshooting
Push Rejected?
Pull first, then push again:
git pull --rebase origin main git push origin main
Not a Git Repository?
git init git remote add origin [URL]
Large Files Issue?
Consider Git LFS for images/attachments.
Integration
Works with:
- `/daily` - Commit after creating daily note
- `/weekly` - Commit after weekly review
- `/onboard` - No git needed for context loading
- Auto-commit hook for automatic saves
Not another PKM starter kit. This is an execution system that connects your 3-year vision to what you do today — and holds you accountable with AI. Every layer connects. /daily surfaces your ONE Big Thing from the weekly review. /weekly shows project progress.
Other skills on obsidian-claude-pkm.
- /adopt
Scaffold the PKM system onto an existing Obsidian vault. Scans your vault structure, maps folders interactively, and generates configuration — no template required.
Open skill - /check-links
Find broken wiki-links in the vault. Read-only analysis — scans for [[links]] and verifies target files exist. No writes, no dependencies.
Open skill - /daily
Create daily notes and manage morning, midday, and evening routines. Structure daily planning, task review, and end-of-day reflection. Use for daily productivity routines or when asked to create today's note.
Open skill - /goal-tracking
Track progress toward 3-year, yearly, monthly, and weekly goals. Calculate completion percentages, surface stalled goals, connect daily tasks to objectives. Use for goal reviews and progress tracking.
Open skill - /monthly
Monthly review and planning. Roll up weekly reviews, check quarterly milestones, set next month's focus. Use at end of month or start of new month.
Open skill - /obsidian-vault-ops
Read and write Obsidian vault files, manage wiki-links, process markdown with YAML frontmatter. Use when working with vault file operations, creating notes, or managing links.
Open skill