Skip to main content

git-pushing

Stage all changes, create a conventional commit, and push to the remote branch. Use when explicitly asks to push changes ("push this", "commit and push"), mentions saving work to remote ("save to github", "push to remote"), or completes a feature and wants to share it.

Quellinformationen

Repository
dark-vex/infra-cd
Letzte Quellaktivität
26. Juli 2026 um 12:40
Erkannte Sprache von SKILL.md
Englisch
Sterne
8
Forks
0

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

Datei-Explorer
2 Dateien

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
git-pushing
description
Stage all changes, create a conventional commit, and push to the remote branch. Use when explicitly asks to push changes ("push this", "commit and push"), mentions saving work to remote ("save to github", "push to remote"), or completes a feature and wants to share it.
risk
critical
source
community
date_added
2026-02-27
disable-model-invocation
true
# Git Push Workflow Stage all changes, create a conventional commit, and push to the remote branch. ## When to Use Automatically activate when the user: - Explicitly asks to push changes ("push this", "commit and push") - Mentions saving work to remote ("save to github", "push to remote") - Completes a feature and wants to share it - Says phrases like "let's push this up" or "commit these changes" ## Workflow **ALWAYS use the script** - do NOT use manual git commands: ```bash bash skills/git-pushing/scripts/smart_commit.sh ``` With custom message: ```bash bash skills/git-pushing/scripts/smart_commit.sh "feat: add feature" ``` Script handles: staging, conventional commit message, Claude footer, push with -u flag. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Auf GitHub ansehen