agentleFS
Sign inStart free
kv0906kv0906/pm-kit/.claude/skills/push/SKILL.md

push

Skill138 starsChanged 7 months agoMITView on GitHub

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.

  • Reads credentials
  • Commits and pushes

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 41 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Verify Git repository exists

    line 67
  2. Distinctive:

    Check for uncommitted changes

    line 68
  3. Distinctive:

    Ensure remote is configured

    line 69
  4. Distinctive:

    Never force push without explicit request

    line 70

“Common” is measured: kept by at least 6 in 10 of the 41 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/push — Git Push

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 sprint 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:
      • Counts files by folder type (daily, docs, blockers, etc.)
      • Summarizes key modifications
    • Includes date/time stamp
  3. Syncs with Remote
    • Pulls latest changes (rebase)
    • Pushes to remote repository
    • Handles merge conflicts gracefully

Commit Message Format

Automatic Messages

Based on your changes:

[2026-01-15] Daily note + 2 blocker updates + 1 decision

With Custom Message

[2026-01-15] Completed sprint planning

Git Operations

Standard Flow

  1. git add . - Stage all changes
  2. git commit -m "message" - Create commit
  3. git pull --rebase - Get remote changes
  4. git push - Push to remote

Safety Checks

  • Verify Git repository exists
  • Check for uncommitted changes
  • Ensure remote is configured
  • Never force push without explicit request

Security Considerations

Never Commit

  • .env files or credentials
  • API keys or tokens
  • Personal identification

Use .gitignore for

.obsidian/workspace*
.obsidian/cache
.trash/
.DS_Store

Download now (ZIP)

  • Other versions47 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 47

    1. openai/symphony★ 27ksame name
    2. kdlbs/kandev★ 1ksame name
    3. cashew-labs/libretto★ 898same name
    4. saffron-health/libretto★ 883same name
    5. egregore-labs/egregore★ 293same name
    6. Mooshieblob1/MooshieUI★ 213same name
    7. team-mirai-volunteer/mirai-gikai★ 212same name
    8. sterlingcrispin/claude_slash_commands★ 200same name
    9. Nucleify/Nucleify★ 171same name
    10. atherio-danp/cde-dotnetcc★ 109same name

    37 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use get-pr-reviews, push-everything and 9 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • saffron-healthSkill

      get-pr-reviews

      Get nicely formatted output of the last review comments on a PR. Used internally by other skills.

      Also in 3 projects that use this

    • saffron-healthSkill

      push-everything

      Stage ALL changes in the repository (not just session changes), commit, and push. Use when you need to commit all pending changes.

      Also in 3 projects that use this

    • NVIDIASkill

      generate-spec

      Produce a feature specification covering API changes, backward compatibility, cross-language impact, performance, and a file-level change plan. Use when designing a new feature, planning a significant change, or the user asks to spec something out.

      Also in 3 projects that use this

    • MicrosoftSkill

      merge

      Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.

      Also in 3 projects that use this

    • AWSSkill

      implement-spec

      Implement the result of /to-spec and /to-tickets in code.

      Also in 4 projects that use this

    • MicrosoftSkill

      spec-review

      Independent, multi-model review of a design or spec **before** any code is written, for the microsoft/winappcli repo. Activate when a contributor asks to "review this spec", "review my design", "review this design doc", "validate this approach", "should we build this", "spec review", "design review", or "feature review". Fans out parallel sub-agents — each doing its OWN research against the real codebase and ecosystem rather than trusting the spec — covering necessity & scope, approach & alternatives, feasibility vs reality, risks & unknowns, DX & user impact, and a different-model-family cross-check. Emits a decision-oriented recommendation (proceed / proceed-with-changes / reconsider) to stdout. This is the PRE-CODE companion to the pr-review skill (which reviews code already written); use spec-review at the design/spec stage, not on an implemented diff. Does NOT write code or edit the spec.

      Also in 3 projects that use this

    • +2 more from saffron-health
  • In this repository41 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free