Programowanie · Automatyzacja
modernize
/modernize
Aktualizuje stare merge requesty do aktualnej gałęzi docelowej przez rebase, w GitLab lub GitHub, na prośbę użytkownika.
Dla kogo
- Autor
- Wozacosta ↗
- Repozytorium
- forgestack ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 28.10.2026
Ocena i bezpieczeństwo
90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Przestarzałość
Brak sygnałów. Repozytorium zmienione 28.10.2026, bez odwołań do wycofanych modeli i API.
Licencja
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Aktualizuje stare merge requesty do aktualnej gałęzi docelowej przez rebase, w GitLab lub GitHub, na prośbę użytkownika.
Wyzwalacze z opisu
modernize
Oryginalny opis (EN)
For getting old merge requests up to date. Use when asked to rebase an MR (or a PR on GitLab) or "modernize".
Jak działa
- Guardrails
- Establish the MR's intent
- Check what changed around it
- Choose a disposition before pushing
- Rebase without losing intent
- Report
Sekcje z nagłówków SKILL.md, w oryginale · 102 linii, 730 słów
Podgląd SKILL.md
--- name: modernize description: >- For getting old merge requests up to date. Use when asked to rebase an MR (or a PR on GitLab) or "modernize". --- # Modernize Modernize the idea, not just the branch. A clean rebase does not prove that the MR still belongs in the product. ## Guardrails - Always check to make sure you have pulled latest origin for your branch, the target branch, and any other branch related to your work before starting. - Treat existing worktree changes as user-owned. Use a disposable worktree when the active worktree is dirty or is being used for other work. - Modernizing authorizes rebasing and updating the MR's source branch. It does not authorize merging, closing, changing the target branch, or expanding 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 an MR comment unless the user asked for one. Use the `leaving-mr-comments` skill for every comment posted on the user's behalf. ## Establish the MR's intent Resolve the MR (`glab mr view <iid> -F json`) and record its URL, state, target branch, source project and branch, current head SHA, author, pipeline status, approvals, and threads. Read the title, description, linked issues, commits, review threads, and complete diff. State the smallest coherent goal the MR was trying to accomplish before judging its implementation. Fetch the latest remote target and MR head. Use the MR's actual target branch, usually `main`, rather than assuming the local branch is current. Record the merge base so the original MR and subsequent target-branch changes can be compared separately. ## Check what changed around it Inspect commits and diffs added to the target branch since the MR diverged. Search merged and open MRs (`glab mr list --merged --search <terms>`) when titles, code paths, or behavior suggest a replacement or competing implementation. Look beyond overlapping lines: - Has the same user-facing problem already been solved? - Did APIs, types, schemas, dependencies, or architectural boundaries change? - Do both sides now claim ownership of the same behavior or invariant? - Was the code being changed deleted, moved, or intentionally simplified? - Would landing the MR restore an old behavior or create two ways to do the same thing? - Is the original benefit still large enough to justify the maintenance cost? Do not describe an MR as current merely because Git reports no conflicts. ## Choose a disposition before pushing Use one of these recommendations: - **MODERNIZE**: the goal is still useful and the implementation remains the right shape. Rebase, resolve conflicts, test, and update the branch. - **REWORK**: the goal is still useful, but a mechanical rebase would preserve the wrong implementation. Explain the smallest credible rewrite and stop before pushing unless the user also asked for that rework. - **CLOSE**: the MR is superseded, obsolete, directionally wrong, or no longer worth its cost. Cite concrete evidence and stop. Do not spend time rebasing an obsolete branch, and do not close it without explicit permission. Be willing to recommend `CLOSE`. Age alone is not evidence, and sunk effort is not a reason to keep an MR alive. ## Rebase without losing intent For a `MODERNIZE` disposition: 1. Create a safe local branch or disposable worktree at the recorded MR head. 2. Rebase its commits onto the freshly fetched target branch. (`glab mr rebase` only works without conflicts and skips the checks below, so prefer a local rebase.) 3. Resolve each conflict according to the MR's current intent and the target branch's newer invariants. If a conflict reveals a product or architecture disagreement, stop and reconsider the disposition instead of guessing. 4. Compare the pre-rebase and post-rebase commit series with `git range-diff` and inspect the final diff. Confirm that no intentional behavior disappeared and no already-landed behavior was reintroduced. 5. Run the repository's focused checks for the touched area. Distinguish real failures from pre-existing or infrastructure failures. 6. Push with `--force-with-lease` tied to the previously observed remote head. If the lease fails, fetch and reassess rather than overwriting new work. Do not merge the MR. ## Report Lead with `MODERNIZE`, `REWORK`, or `CLOSE` and the reason. Then summarize: - meaningful changes on the target branch; - conceptual conflicts or confirmation that none were found; - the rebase and push result, if performed; - checks run and their results; - the remaining decision or work, with a link to the MR. Separate observed facts from judgment. Say what could not be verified instead of manufacturing confidence.
Pliki w paczce (2)
- SKILL.md 5 KB
- agents/openai.yaml 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · Wozacosta/forgestack | 90 | MIT |
| colinmollenhour/dotfiles | 100 | Apache-2.0 |
| gvaldesmty1/modernia | 100 | MIT |
| cravingmaker/skills | 100 | MIT |
| bendrucker/claude | 100 | MIT |
| gosuda/dalcom-skills | 95 | Apache-2.0 |
| adelrodriguez/skills | 90 | MIT |
| NathanColosimo/skills | 86 | MIT |
| t3dotgg/tstack | 86 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 8f0604eb92db (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
- 81t3-modernize
Aktualizuje stare pull requesty przez rebase i modernizację, gdy użytkownik o to prosi. - 100pr-modernize
Ocenia stary PR względem aktualnej bazy, rebasuje go, jeśli cel nadal ma sens, i nie scala ani nie zamyka. - 92gitlab
Obsługuje repozytoria, merge requesty i API GitLab przez zmienną GITLAB_TOKEN oraz zarządza zasobami hostowanymi na GitLab. - 100pr-modernize
Ocenia, czy stary lub odziedziczony PR powinien wejść do bazy, rebasuje go i zachowuje autorstwo pierwotnych autorów. - 100gitlab
Obsługuje przez glab CLI zgłoszenia, merge requesty, repozytoria, potoki CI i wyszukiwanie kodu w GitLab, także na własnej instancji. - 100glab
Tworzy, czyta, aktualizuje i zamyka issues oraz merge requesty GitLab przez glab CLI.