Menü
Automates committing and pushing changes while ensuring a clean history of a single commit. Use when requested to commit and push changes, especially when pre-commit hooks or remote conflicts are expected.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
How to create a new API backend service in the GetBlitz API using Dependency Injection. Use this when the user asks to implement or add a new backend service.
How to add and structure UI components in the GetBlitz interface. Use this when tasked with building frontend UI or components.
How to add or modify tRPC routes in the GetBlitz API. Use this when you need to expose a service through the API or create a new endpoint.
| name | git-safe-commit-push |
| description | Automates committing and pushing changes while ensuring a clean history of a single commit. Use when requested to commit and push changes, especially when pre-commit hooks or remote conflicts are expected. |
This skill automates the process of committing and pushing changes, with built-in error handling for pre-commit hooks and remote conflicts, ensuring that only a single commit is pushed for the current task.
git reset --soft HEAD~1. This keeps your changes staged.git pull --rebase. This fetches remote changes and applies your staged changes on top.git add . and git rebase --continue (or follow git's instructions).git commit -m "[original message]" (or use git commit -C ORIG_HEAD to reuse the message).git push again.The goal of this skill is to avoid "fixup" or "merge" commits on the remote. By using git reset --soft and git pull --rebase, we ensure that the final result on the remote is a single, clean commit containing both the original work and any necessary fixes or remote updates.
git status after a successful push to ensure the working directory is clean and the branch is up to date with the remote.