st-revive
/st-revive
Odświeża stary PR: sprawdza, czy jego pomysł pasuje do obecnego kodu, a potem robi rebase, przerabia go albo zaleca zamknięcie.
- Autor
- 58fly ↗
- Repozytorium
- dsh-stack ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 08.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 08.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Odświeża stary PR: sprawdza, czy jego pomysł pasuje do obecnego kodu, a potem robi rebase, przerabia go albo zaleca zamknięcie.
Oryginalny opis (EN)
Brings an old PR up to date by checking if its idea still fits the current code, then rebasing, reworking or recommending it be closed. Use when asked to rebase, refresh, update or revive a stale PR, or /st-revive.
Jak działa
- Steps
- Stop when
- Rules
Podgląd SKILL.md
--- name: st-revive description: "Brings an old PR up to date by checking if its idea still fits the current code, then rebasing, reworking or recommending it be closed. Use when asked to rebase, refresh, update or revive a stale PR, or /st-revive." --- Update the idea, not only the branch. A clean rebase does not prove the PR still belongs. ## Steps 1. Fetch the latest base, the PR head and any related branches. 2. Record the PR URL, state, base, head branch, head SHA, author, checks and review state. Read the title, body, linked issues, commits, threads and full diff. 3. Write the PR's goal in one sentence. 4. Find the merge base. Read what landed on the base branch since then. Search merged and open PRs for the same problem. 5. Answer each question with evidence (commit, PR or file path): - Has this problem already been solved? - Did the APIs, types, schemas or structure it relies on change? - Was the code it edits moved, deleted or simplified? - Would landing it bring back old behavior or make two ways to do one thing? - Is the benefit still worth the upkeep? 6. Pick one verdict: - **REVIVE**: goal and shape still fit. Go to step 7. - **REWORK**: goal fits, shape does not. Describe the smallest rewrite and stop, unless the user also asked for the rework. - **CLOSE**: superseded or no longer worth it. Cite the evidence and stop. Do not close it yourself. 7. For REVIVE: work in a clean worktree at the recorded head. Rebase onto the fresh base. Resolve conflicts by the PR's goal and the base's newer rules. 8. Run `git range-diff` on the old and new series. Confirm no intended change was lost and nothing already landed came back. 9. Run the focused checks for the touched area. Mark each failure as real, pre-existing or infrastructure. 10. Push with `--force-with-lease=<branch>:<old head SHA>`. 11. Report the verdict first, then base changes, conflicts, push result, checks and the remaining decision with the PR link. ## Stop when - The report is written after any of the three verdicts. - A conflict shows a product or design disagreement. Stop and reconsider the verdict. - The lease fails. Fetch again and redo steps 4 to 6 once. If it fails again, report. ## Rules - Treat a dirty worktree as the user's. Never stash or discard it. - Never merge, close or change the base branch. Never force-push without a lease. - No conflicts in Git does not mean the PR is current. - Separate facts you checked from your judgment. - Post PR comments only when asked, through `st-pr-comments`.
Wersje
W bazie nie ma innych skilli o nazwie st-revive.
Migawka bazy z 13.11.2026 · wersja paczki 4d3bd82a6eee (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90ds-revive
Odświeża stary PR: sprawdza, czy jego pomysł pasuje do obecnego kodu, a potem rebasuje, przerabia albo sugeruje zamknięcie. - 100workflow-refresh
Odświeża stary pull request po zmianach w gałęzi bazowej i rekomenduje odświeżenie, przepisanie albo zamknięcie z dowodami. - 100pr-modernize
Ocenia, czy stary lub odziedziczony PR powinien wejść do bazy, rebasuje go i zachowuje autorstwo pierwotnych autorów. - 100modernize
Ocenia stary pull request lub merge request względem aktualnego produktu i kodu, a jeśli nadal jest przydatny, robi rebase i aktualizuje go, na wyraźną prośbę o odświeżenie przeterminowanego PR. - 86modernize
Odświeża stare pull requesty przez rebase, gdy użytkownik prosi o rebase albo o modernize. - 96refresh
Aktualizuje gałąź pull requesta przez rebase, gdy użytkownik prosi o odświeżenie.