Menú
Use when validating a set of PRs together on a staging branch before advancing the base branch.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Demolish bloated code and re-derive it clean, cutting every surface the rebuilt contract does not name. Use for a repo-wide bloat sweep, when patching a subsystem has stopped paying, or when the user says "this whole module is bloated", "rewrite this properly", or "break it and rebuild".
Use when the user says "deslop", "remove debug code", "find placeholders or stub code", or "remove dead code".
Dispatch compress operations. Use when the user says "tidy" or names a file, diff, memory, workspace, git stack, or doc to tidy.
Reduce internal duplication, dead code, and ceremony. Use when you spot dead fields, redundant wrappers, or speculative abstractions in code you are already editing.
Use when modernizing APIs, removing compat shims, killing feature flags, or rewriting a subsystem cleanly.
Use when the user says "simplify this diff", or asks for a compression pass over a change-set.
| name | pr-merge-temporal |
| description | Use when validating a set of PRs together on a staging branch before advancing the base branch. |
Merge multiple PRs into a temporal integration branch for validation before merging to base.
Detect base branch: Identify the default branch via git remote show origin or repo conventions.
Enumerate PRs: List all PRs to merge. For each, fetch the latest HEAD.
Create temporal branch: Fetch latest and branch from the remote base tip.
git fetch origin
git checkout -b temporal/<timestamp> origin/<base>
Determine merge order:
Sequential merge with conflict handling: for each PR in order:
a. Attempt git merge --no-ff <pr-branch> into the temporal branch.
b. If merge succeeds cleanly, continue to next PR.
c. If conflicts occur:
difft and codebase context.git merge --abort), stop, and report the conflict with both sides and a recommended resolution.
d. After each successful merge, run available build/test commands to catch regressions early.Validate temporal branch: Once all PRs are merged, run full build/test suite if available.
Report results: Present the validated temporal branch to the user. Only advance base if the user explicitly requests it.
Abort conditions: stop the queue and report if:
git checkout <base>. Base remains untouched.Report for each PR: merged successfully, conflicts resolved (with details), or blocked (with reason). Include the temporal branch name for user review.