pull-requests
/pull-requests
Finalizuje pull request, gdy zmiana działa i ma trafić do przeglądu, także przy aktualizacji istniejącego PR.
- Autor
- systemfsoftware ↗
- Repozytorium
- systemfsoftware ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 25.10.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 25.10.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Finalizuje pull request, gdy zmiana działa i ma trafić do przeglądu, także przy aktualizacji istniejącego PR.
Oryginalny opis (EN)
Pull request finalization. Use when a change works and is about to be opened as a pull request, or when updating or continuing an existing one.
Jak działa
- Workflow
Podgląd SKILL.md
--- name: pull-requests description: Pull request finalization. Use when a change works and is about to be opened as a pull request, or when updating or continuing an existing one. --- A pull request is ready when its tests, implementation, comments, and changeset are each the simplest that cover the intended behavior. Draft PRs can be used earlier; finishing means making the PR ready for review. ## Workflow Run each step in a fresh-context subagent when available; otherwise run it yourself. Pass along the task context and prior results so each step can check its gate. 1. Keep tests focused. Read [test-development](../test-development/SKILL.md) for test placement and type. Cover each intended behavior once, in the existing test file for the module. For changes needing no tests, record why. Continue when removing any remaining case would leave intended behavior uncovered, or no tests are needed. 2. Simplify the implementation. With the tests passing, look for a simpler or more idiomatic version: reuse helpers and patterns from nearby source and [effect-development](../effect-development/SKILL.md), and remove debugging code, scaffolding, and changes unrelated to the task. Continue when applicable targeted tests pass and every hunk in the diff from the merge base is required by the task. 3. Review the full diff from the merge base as a maintainer would: correctness, failure and interruption paths, resource cleanup, naming and API consistency with neighboring modules, and documentation. Fix findings and review again. Continue when a review pass produces no findings. 4. Clean up. Remove comments that restate code or narrate the change; keep the rest short and about why. Finalize the changeset with [changesets](../changesets/SKILL.md). Continue when comments explain only what code cannot, and the changeset describes the final consumer impact or the no-changeset reason is recorded. 5. Run the validation in the [AGENTS.md validation table](../../AGENTS.md#validation) for each change type in the diff. Fix failures caused by the change; if fixes alter the diff, repeat the affected passes. Continue when applicable checks pass or commands that cannot run and their blockers are recorded. 6. Open or update the pull request. Title: a short imperative summary. Description: the problem addressed, notable decisions, and `Closes #<issue>` for each GitHub issue resolved. Do not narrate the diff. Mark the PR ready for review. Continue when the final changes are pushed, the description matches the final diff, and the PR is ready for review. The task is complete when each step's gate holds, validation has passed or been reported as not runnable with reasons, and the pull request is ready for review with a description matching the final diff.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · systemfsoftware/systemfsoftware | 86 | Apache-2.0 |
| microsoft/agent-framework | 100 | MIT |
| microsoft/agent-framework | 100 | MIT |
| microsoft/agent-framework | 100 | MIT |
| modem-dev/ossrules | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki aaa65c3483a7 (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
- 80pull-request:create
Tworzy pull request, merge request lub change request, także zaraz po zatwierdzeniu zmian w repozytorium. - 100pull-request-standards
Pisze czytelne opisy pull requestów dla współtwórców repozytorium przy tworzeniu i aktualizacji PR. - 100write-pull-request
Pisze czytelne commity i opisy pull requestów, które recenzent sprawdzi szybko, także przy ich aktualizacji. - 100pr-writing
Pisze opisy pull requestów z prawdziwymi dowodami, że zmiana działa, zamiast samego opisu zmian. - 100rails-cto-pull-request
Tworzy pull request do gałęzi staging za pomocą gh CLI, gdy kod ma trafić do przeglądu. - 100creating-pr
Tworzy pull requesty GitHub z wykrywaniem istniejącego PR, pushem gałęzi i generowaniem tytułu oraz treści, także dla aktualizacji i szkiców.