Menü
Use when the user asks to rebuild a feature branch into a clean, reviewable git history
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
Use when the user says they are stepping away and the agent should continue without interactive approvals
Use when running e2e tests, debugging test failures, or fixing flaky tests. Covers failure taxonomy, fix rules, and workflow. Never changes source code logic or API without spec backing.
Use when auditing how well the shared agent instructions (AGENTS.md, skills) hold up in real sessions — sampling transcripts via recall, scoring them against the gap rubric, and turning findings into ratified amendments
Use when preparing clean, logical git commits from an existing working tree
Use when syncing a feature branch onto the latest origin base branch via git rebase.
Fetch latest from origin, prune remote-tracking refs, delete stale local branches and worktrees, and fast-forward important branches. Use when tidying up a worktree-based repo layout.
| name | rewrite-history |
| description | Use when the user asks to rebuild a feature branch into a clean, reviewable git history |
Rewrite branch history only when the user explicitly asks. That invocation authorizes the local rewrite: resets and rebases behind the backup tag are reversible interior work — print each command as status and proceed.
--force-with-lease push to your own
non-deploying feature branch is a proposal needing no extra authorization;
a shared (other authors, collaborative PR) or deploy-tracked ref is a
publish — restate the ref and leave it to the user.git-rebase-sync skill's conflict ladder; if genuinely stuck, stop with an
honest block: what was tried, why it cannot converge, and a proposed path.