Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

push-after-rebuild

Sterne65

Forks8

Aktualisiert29. Mai 2026 um 13:37

When the user wants to push, commit, or "save to git", first rebuild the app and only proceed with commit and push if the build succeeds. Use when the user says push, commit and push, or deploy changes to git.

Installation

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.

In Manus ausführen

Quelle

mgsgde

mgsgde/whisper-shortcut

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	push-after-rebuild
description	When the user wants to push, commit, or "save to git", first rebuild the app and only proceed with commit and push if the build succeeds. Use when the user says push, commit and push, or deploy changes to git.

Push Only After Rebuild

Before any commit or push: rebuild first (follow the always-applied rebuild rule in .cursor/rules/index.mdc). If the build fails, stop — inform the user and do not commit or push.

Flow

Rebuild. Fails → stop. Succeeds → continue.
Commit (only if this chat made changes). Stage only the files you edited in this conversation — never git add -A, so work from other chats/sessions stays out. Exception: the user explicitly asks to "commit everything".
```
git status
git add <file1> <file2> ...
git commit -m "..."
```
Push (git push). For a release, push the branch first, then the release tag.

Commit-only requests (no push) and push-only requests (nothing new to commit) still rebuild first.

Mehr aus diesem Repository

gleiches Repository

analyze-chat-freeze

mgsgde/whisper-shortcut

Triage a WhisperShortcut chat-window main-thread freeze from the watchdog's on-disk hang captures and app logs — classify real vs. false-positive, localize the wedge, confirm whether the shipped fix held, and continue root-causing new variants. Use when the app beachballs/freezes/pins CPU during chat, when a new hang-*.txt appears, or when asked to investigate a chat hang.

2026-07-0565

run-whisper-shortcut

mgsgde/whisper-shortcut

Build, launch, drive, screenshot, and walk through the WhisperShortcut macOS menu-bar app from a user's perspective. Use when asked to run, start, launch, build, screenshot, test onboarding, cognitive walkthrough, first-run activation, or visually confirm UI changes in the real app (not just tests). Covers Welcome onboarding, status menu, Settings, and Chat.

2026-06-2965

analyze-user-interactions

mgsgde/whisper-shortcut

Mine the local user-interaction JSONL logs for systematic failures and propose improvements across system prompts, defaults, code logic, logging, and UI. Use when the user asks for improvements based on actual usage — e.g. "what's going wrong in Dictate Prompt?", "analyze my recent interactions", "find patterns in the logs", "what should we improve based on how I'm using the app?".

2026-06-2965

validate-audio-verification

mgsgde/whisper-shortcut

Validate end-to-end that Smart Improvement audio verification is actually working — audio is captured for dictation, selected content-aware to verify recurring candidate terms, attached only when the asymmetry rule passes, used by the dictation and Whisper Glossary focuses, and retained across runs (pruned by age). Use when the user asks "is audio verification working?", after implementing or modifying the Smart Improvement audio verification feature, or when investigating why a glossary/dictation suggestion was or was not produced.

2026-06-2965

audit-llm-context

mgsgde/whisper-shortcut

Systematically reviews all LLM-context files in this repo (.cursor/commands/, .cursor/rules/, .cursor/skills/) for stale references, factual drift vs the current codebase, redundancy across files, and files that no longer earn their slot. Produces a tiered report (broken / drift / dedup / hygiene). Use when the user asks to audit, review, check, or validate LLM-context files, cursor rules, claude skills, prompt files, or "are these instructions still correct".

2026-06-0565

llm-model-docs

mgsgde/whisper-shortcut

Look up current official documentation AND current model lineups for OpenAI, Google Gemini, and xAI (Grok). Use BEFORE adding/changing model IDs, before answering model-capability questions (e.g. "does gpt-4o-transcribe accept a system prompt?"), AND proactively whenever you touch chat/transcription/TTS code paths (provider files, SettingsConfiguration, TranscriptionModels, ChatModelCommandResolver, SpeechService) — compare our current defaults to what each provider has shipped recently, and surface upgrade suggestions to the user if newer GA models exist. AI moves fast — always check live docs first.

2026-06-0565

name	push-after-rebuild
description	When the user wants to push, commit, or "save to git", first rebuild the app and only proceed with commit and push if the build succeeds. Use when the user says push, commit and push, or deploy changes to git.

Push Only After Rebuild

Before any commit or push: rebuild first (follow the always-applied rebuild rule in .cursor/rules/index.mdc). If the build fails, stop — inform the user and do not commit or push.

Flow

Rebuild. Fails → stop. Succeeds → continue.
Commit (only if this chat made changes). Stage only the files you edited in this conversation — never git add -A, so work from other chats/sessions stays out. Exception: the user explicitly asks to "commit everything".
```
git status
git add <file1> <file2> ...
git commit -m "..."
```
Push (git push). For a release, push the branch first, then the release tag.

Commit-only requests (no push) and push-only requests (nothing new to commit) still rebuild first.