Skip to content

sterlingcrispin/claude_slash_commands / push

Commit and push changes with auto-generated summary

FileKindSize
SKILL.mdskill md948 B
---
description: Commit and push changes with auto-generated summary
allowed-tools: Bash(git:*)
---

# 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.)
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse 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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall