finish-work
/finish-work
Domyka gotową zmianę: sprawdza dokumentację, uruchamia pełną bramkę, tworzy commit, otwiera szkic PR i prosi opiekuna o scalenie.
- Autor
- serionist ↗
- Repozytorium
- claude-sticky ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.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 12.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
Domyka gotową zmianę: sprawdza dokumentację, uruchamia pełną bramkę, tworzy commit, otwiera szkic PR i prosi opiekuna o scalenie.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use when a change is ready ("finish", "wrap up", "we're done", "open the PR"). Checks the docs moved with the change, runs the full gate with the plugin's types, tries in a real session what no test can reach, commits, opens a draft PR, reviews it with review-code until it is clean, and asks the maintainer to mark it ready or merge it; the maintainer squash-merges.
Jak działa
- Steps
- Done means
- Never
Podgląd SKILL.md
---
name: finish-work
description: >-
Use when a change is ready ("finish", "wrap up", "we're done", "open the PR"). Checks the docs moved with the
change, runs the full gate with the plugin's types, tries in a real session what no test can reach, commits, opens a
draft PR, reviews it with review-code until it is clean, and asks the maintainer to mark it ready or merge it; the
maintainer squash-merges.
---
# Finish a change
Done means `node tools/gate.ts full` passed, `REVIEW.md` is answered and `review-code` is clean, not that the work
feels complete. `main` takes PRs only, and the maintainer squash-merges them (`AGENTS.md`, How a change lands).
## Steps
1. **Docs in the same change.** Check each thing that describes the change moved with it: `README.md` and
`plugin/README.md` for what users see (a command, a setting, a key, what the plugin keeps or adds to Claude's
context), `docs/design.md` for how it works, `CHANGELOG.md` under Unreleased when users notice it, `AGENTS.md` for a
changed path, command or rule, and the plan when the work departed from it (where and why). Write them the way
`AGENTS.md` asks.
2. **The plugin's types.** For a change under `plugin/`: is `plugin/.claude-plugin/types/` there, written by the Claude
Code you run? If not, load the mod once (`claude --plugin-dir plugin`, then quit), so the gate checks the types
instead of skipping them. CI can't.
3. **The gate:** `node tools/gate.ts full`. Fix every failure; never weaken a test, a check or an ignore to pass.
4. **Try it in a real session,** for a change a test can't reach (closing the pane, the scroll to the transcript, a
notification, a restart, how Claude reads changed text): with the installed copy turned off
(`claude plugin disable sticky@sticky`), start `claude --plugin-dir plugin` in a scratch folder and run the checks
in `docs/testing-by-hand.md` that the change touches. Note the system, terminal and Claude Code versions, what
worked, and what you could not show (the desktop app, a narrow terminal, another system). Turn the installed copy
back on.
5. **Commit:** a plain imperative subject that says what changed, a body that says why, `Refs #<n>`. No tool
attribution: `commit-msg` refuses it.
6. **Open a draft PR.** Write the body to `.local/pr-body.md` from `.github/pull_request_template.md`. Push with
`git push -u origin HEAD` (`pre-push` runs gate quick), then `gh pr create --draft --title "<plain imperative
sentence>" --body-file .local/pr-body.md`. The title becomes the commit subject on `main`. Say it's open and how
to see it all: the PR's Files tab, or `git diff origin/main...HEAD`.
7. **Review** with `review-code` until it is `clean`. Commit each round's fixes with gate quick passing, and the
record in `docs/reviews/`. Put the verdict and the record's path in the body's Review section:
`gh pr edit <n> --body-file .local/pr-body.md`.
8. **CI** on the head commit: `gh pr checks <n> --watch`. A red check is fixed, never skipped.
9. **Ask the maintainer,** as one question with a recommendation: mark it ready (`gh pr ready <n>`), merge it, or
leave it a draft.
- If `main` moved: `git fetch origin`, `git rebase origin/main`, `git push --force-with-lease`. A rebase that
changes code needs the gate again.
- Merge only on the maintainer's word: `gh pr merge <n> --squash --delete-branch --subject "<title> (#<n>)"
--body-file .local/squash.md`, a body that says what and why and ends `Refs #<issue>` or `Closes #<issue>`. No
HTML comments, no tool attribution.
10. **Clean up** after the merge: `git switch main` and `git pull`; a worktree goes with `git worktree remove <path>`
from the main checkout. Work that turned up on the way becomes an issue (`gh issue create`).
## Done means
- `gate full` passed on the head commit with the plugin's types checked, `review-code` is clean for exactly this code,
and the PR says how what no test reaches was tried.
- The PR is ready for the maintainer, merged on their word, or left a draft by their choice.
## Never
- Open, mark ready or merge a PR with a failing gate or CI, or with a review of different code.
- Mark a `REVIEW.md` question yes without its evidence.
- Add AI co-author trailers, "Generated with" lines or session links: commits, PR titles, PR bodies.
- Push to `main`, merge without the maintainer's word, or push to someone else's branch.
- Bump `plugin.json`'s version outside a release PR (`docs/releasing.md`).
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · serionist/claude-sticky | 90 | MIT |
| serionist/claude-session-restore | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki c638b8c6b0e6 (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
- 90finish
Domyka gotową pracę: sprawdza testy, proponuje scalenie, PR, zachowanie lub odrzucenie gałęzi i wykonuje wybraną opcję. - 86verify-change
Sprawdza gotową zmianę: czyta diff, uruchamia najmniejszą sensowną weryfikację i wywołuje recenzentów wymaganych przez bramkę zakończenia. - 86verify-change
Sprawdza gotową zmianę: czyta diff, uruchamia najmniejszą sensowną weryfikację i wywołuje recenzentów wymaganych przez bramkę zakończenia. - 100finish
Domyka zakończone zadanie: samoocenę, decyzje, retrospektywę, commit plików zapisu, scalenie i raport, gdy przeszło bramkę piątą. - 100finish-task
Przeprowadza gotowe zadanie przez uproszczenie, przegląd, ocenę, commit i pull request w tej kolejności. - 100finish-issue
Domyka zrealizowane zgłoszenie: sprawdza pull request lub lokalną gałąź, scala ją przez squash i potwierdza zamknięcie.