← ClaudeAtlas

revivelisted

Bring a stale pull request up to date by judging whether it still belongs in the product before rebasing it, and recommending modernize, rework or close. Use when asked to revive, refresh, rebase or modernize an old PR, or what to do with a PR that has gone stale.
Udhay-Adithya/skills · ★ 0 · AI & Automation · score 70
Install: claude install-skill Udhay-Adithya/skills
# Revive Revive the idea, not just the branch. A clean rebase does not prove the PR still belongs in the product. ## Guardrails - Pull the latest origin for this branch, the base branch, and any other branch related to the work before starting. - Treat existing worktree changes as owned by the user. Use a disposable worktree when the active one is dirty or in use. - Reviving authorizes rebasing and updating the PR branch. It does not authorize merging, closing, changing the base branch, or widening scope. - Never use an unqualified force push. Update a rebased branch with `--force-with-lease` against the head SHA observed before the rebase. - Do not post a PR comment unless one was asked for. Use the `remark` skill for every comment posted on someone's behalf. ## Establish the PR's intent Resolve the PR and record its URL, state, base, head repository and branch, current head SHA, author, checks and review state. Read the title, body, linked issues, commits, review threads and the complete diff. State the smallest coherent goal the PR was trying to accomplish, before judging how it went about it. Fetch the latest remote base and PR head. Use the PR's actual base branch rather than assuming the local branch is current. Record the merge base, so the original PR and later base-branch changes can be compared separately. ## Check what changed around it Inspect the commits and diffs added to the base branch since the PR diverged. Search merged and open PRs when ti