mcpbeat

Push

sterlingcrispin/push

Commit and push changes with auto-generated summary

237 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
201
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/sterlingcrispin/claude_slash_commands --skill push

The instruction itself

3 sections, as written by the author

Commit and Push Changes

Current State

  • Git status: !git status
  • Staged changes: !git diff --cached
  • Unstaged changes: !git diff

Your Task

  • Review all changes (both staged and unstaged)
  • Update documentation if appropriate:
  • agents.md - Update if pipeline, findings, or project status changed
  • README.md - Update if user-facing docs need to reflect changes
  • Stage all relevant changes with git add
  • Create a clear, concise commit message that summarizes what was changed and why
  • Commit the changes
  • Push to the remote repository

Follow these commit message guidelines:

  • Use imperative mood ("Add feature" not "Added feature")
  • Keep first line under 50 characters
  • Focus on the "what" and "why", not the "how"

Important: Do not commit files that contain secrets (.env, credentials, etc.)

How to use it

Copy the folder

Take sterlingcrispin/push from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.