---
name: Push
slug: push-3
category: DevOps
description: Push commits changes, creates a concise summary, and pushes them to the remote. Use it after reviewing staged and unstaged work and updating docs when needed.
github: "https://github.com/sterlingcrispin/claude_slash_commands/tree/main/push"
stars: 200
forks: 18
install: "npx degit https://github.com/sterlingcrispin/claude_slash_commands/tree/main/push ~/.claude/skills/push"
installs_to: ~/.claude/skills/push
source_path: push/SKILL.md
collection_size: 11
category_size: 973
collection_url: "https://dirskills.com/collections/sterlingcrispin/claude_slash_commands"
added: 2026-09-05T05:30:56.401Z
last_synced: 2026-09-05T05:30:56.401Z
canonical_url: "https://dirskills.com/skills/push-3"
---

# Push

Push commits changes, creates a concise summary, and pushes them to the remote. Use it after reviewing staged and unstaged work and updating docs when needed.

**Install:**

```bash
npx degit https://github.com/sterlingcrispin/claude_slash_commands/tree/main/push ~/.claude/skills/push
```

## README

# Commit and Push Changes

## Current State

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

## Your Task

1. Review all changes (both staged and unstaged)
2. **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
3. Stage all relevant changes with `git add`
4. Create a clear, concise commit message that summarizes what was changed and why
5. Commit the changes
6. 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.)