push
starsforks
How to install push?
kv0906/pm-kit/push
$npx -y skills add kv0906/pm-kit --skill pushCommit 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
| 1 | # /push — Git Push |
| 2 | |
| 3 | Automates Git workflow to save your notes with meaningful commit messages and push to remote repository. |
| 4 | |
| 5 | ## Usage |
| 6 | |
| 7 | Invoke with `/push` or ask Claude to save/commit your changes. |
| 8 | |
| 9 | ### Basic Usage |
| 10 | ``` |
| 11 | /push |
| 12 | ``` |
| 13 | |
| 14 | ### With Custom Message |
| 15 | ``` |
| 16 | /push "Completed sprint planning" |
| 17 | ``` |
| 18 | |
| 19 | ## What This Skill Does |
| 20 | |
| 21 | 1. **Stages All Changes** |
| 22 | - Adds all modified files |
| 23 | - Includes new files |
| 24 | - Removes deleted files |
| 25 | |
| 26 | 2. **Creates Smart Commit Message** |
| 27 | - Uses provided message, or |
| 28 | - Auto-generates from changes: |
| 29 | - Counts files by folder type (daily, docs, blockers, etc.) |
| 30 | - Summarizes key modifications |
| 31 | - Includes date/time stamp |
| 32 | |
| 33 | 3. **Syncs with Remote** |
| 34 | - Pulls latest changes (rebase) |
| 35 | - Pushes to remote repository |
| 36 | - Handles merge conflicts gracefully |
| 37 | |
| 38 | ## Commit Message Format |
| 39 | |
| 40 | ### Automatic Messages |
| 41 | Based on your changes: |
| 42 | ``` |
| 43 | [2026-01-15] Daily note + 2 blocker updates + 1 decision |
| 44 | ``` |
| 45 | |
| 46 | ### With Custom Message |
| 47 | ``` |
| 48 | [2026-01-15] Completed sprint planning |
| 49 | ``` |
| 50 | |
| 51 | ## Git Operations |
| 52 | |
| 53 | ### Standard Flow |
| 54 | 1. `git add .` - Stage all changes |
| 55 | 2. `git commit -m "message"` - Create commit |
| 56 | 3. `git pull --rebase` - Get remote changes |
| 57 | 4. `git push` - Push to remote |
| 58 | |
| 59 | ### Safety Checks |
| 60 | - Verify Git repository exists |
| 61 | - Check for uncommitted changes |
| 62 | - Ensure remote is configured |
| 63 | - Never force push without explicit request |
| 64 | |
| 65 | ## Security Considerations |
| 66 | |
| 67 | ### Never Commit |
| 68 | - `.env` files or credentials |
| 69 | - API keys or tokens |
| 70 | - Personal identification |
| 71 | |
| 72 | ### Use .gitignore for |
| 73 | ``` |
| 74 | .obsidian/workspace* |
| 75 | .obsidian/cache |
| 76 | .trash/ |
| 77 | .DS_Store |
| 78 | ``` |
People who liked this also viewed
6 picksType
- caveman-commitUltra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. UsSkillsJul 2026
- git-guardrails-claude-codeSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- setup-pre-commitSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- resolving-merge-conflictsSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- using-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackSkillsJul 2026
- finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanupSkillsJul 2026
