Przejdź do treści
Biblioteka skilli
Programowanie · Przegląd i audyt

ship

/ship

Sprawdza wszystko przed wysłaniem poza komputer, przygotowuje tekst publiczny i listę testów, a commit i push wykonuje dopiero po zgodzie użytkownika.

Repozytorium
workflow ↗
Licencja
MIT
Ostatnia zmiana repozytorium
04.11.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
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 04.11.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

Sprawdza wszystko przed wysłaniem poza komputer, przygotowuje tekst publiczny i listę testów, a commit i push wykonuje dopiero po zgodzie użytkownika.

Wyzwalacze z opisu

s yes to that specific action does it commit as the user
Oryginalny opis (EN)

Pre-flight before anything leaves the device, then the commit and push once the user says yes. Writes the text that would go public in the user's voice, lists every file and commit behind it, pastes real test output, gives numbered hand tests, names what was not verified, then stops. Only after the user's yes to that specific action does it commit as the user's own git identity and push the feature branch. Invoke before any push, PR, comment, deploy or release, or when the user says ship it or push it.

Jak działa

  1. 1. the text
  2. 2. everything that was done
  3. 3. what was tested, with the real output
  4. 4. hand tests
  5. 5. what was not verified
  6. 6. where this goes
  7. 7. safety checks
  8. 8. then stop
  9. 9. on the user's yes, commit then push
Sekcje z nagłówków SKILL.md, w oryginale · 75 linii, 969 słów
Podgląd SKILL.md
---
name: ship
description: Pre-flight before anything leaves the device, then the commit and push once the user says yes. Writes the text that would go public in the user's voice, lists every file and commit behind it, pastes real test output, gives numbered hand tests, names what was not verified, then stops. Only after the user's yes to that specific action does it commit as the user's own git identity and push the feature branch. Invoke before any push, PR, comment, deploy or release, or when the user says ship it or push it.
---

# ship

nothing leaves this device without the user's yes, given now, on the device. this command prepares that decision, stops, and only after a yes to that specific action runs it. it never opens a pr unasked, never merges, never deploys on its own.

produce one block the user can read top to bottom. the first part is what goes public. everything under it is the evidence.

## 1. the text

write what would actually be posted: the commit message, pr description or pr comment, whichever this is going out as.

- the user's voice per `write`. lowercase, short, direct.
- zero em dashes.
- no ai attribution, no co-authored-by, no tooling mention, no "in this session".
- never claim more than was verified. if something was not run, it does not appear here as done.
- what changed and why, not how clever it was.

this part becomes public, so write it properly rather than dumping a changelog. the user reads it, edits it if they want, and only then does it go anywhere.

## 2. everything that was done

under the text, the full record. no summarising, no "and 4 more files".

- `git status --short` and `git diff --stat`, every file listed.
- `git log origin/<branch>..HEAD --oneline` so the commits going out are named. no upstream yet: say so and list all local commits.

## 3. what was tested, with the real output

detect the scripts from `package.json` or the project's equivalent and run them: test, typecheck, lint, build. this is cook's full verify tier.

- paste the actual output. not "tests pass".
- a script that does not exist: say which and that it does not exist. never skip one silently.
- a suite that self skips without a local service: say how many skipped and why. a skip is not a pass.

## 4. hand tests

numbered steps. required, not conditional on the suite failing. for each: what to run or click, what they should see, what would mean it is broken. cover the path a real user takes through what changed, plus the one edge case most likely to bite. if it cannot be followed without asking a question, it is not tight enough.

## 5. what was not verified

name it plainly. anything read but not run, inferred but not measured, or untestable from here (login walls, deploy protection, a missing local service).

## 6. where this goes

target branch, what deploys from it, and the live url if a push to it is a deploy. say "a push to this branch is live" in those words when true.

work goes out on its own `feat/`, `fix/` or `chore/` branch and reaches main through a pull request. name the branch, say whether ci runs on a plain branch push or only once the pr opens, and say what main needs before a deploy from it.

## 7. safety checks

- `git ls-files | grep -iE 'env|key|secret|pem'` and confirm nothing from that list is staged.
- never print more than 4 characters of any secret value.
- working notes, research, trackers, `.env` files and the notes files in `.claude/` (per `/initiate`) are not going out. `AGENTS.md` and `CLAUDE.md` only if the repo already commits them as the team's convention.
- confirm the notes files are ignored here (`git check-ignore .claude/tbd.md`). if not, flag it before anything else.
- `git config user.name` and `git config user.email` are the user's own identity for this remote. if they look wrong, say so now, not after the commit.

## 8. then stop

print the block and wait. do not commit, push, open the pr, merge or deploy, even if the user approved a similar thing earlier in the session. a yes for one thing is not a yes for the next one.

## 9. on the user's yes, commit then push

only after a yes to this specific action, in this session, on this device. a relayed yes is not one. then exactly this, and nothing more:

1. confirm the branch: `git branch --show-current`. on main or the prod branch: stop and ask, never commit there unless the repo's `.claude/CLAUDE.md` records that standing exception.
2. stage only the files listed in section 2: `git add <each path>`. never `git add -A` or `git add .`. check `git status --short` shows no notes file or anything from the safety list staged.
3. commit with the approved text, byte for byte, as the user's configured git identity: `git commit -F <file with the approved message>`. no `--author` override, no `Co-Authored-By` trailer, no tool mention. if a commit hook rewrites or rejects it, stop and show the output.
4. no remote (`git remote` prints nothing): say so and stop after the commit.
   push the feature branch: `git push -u origin <branch>` the first time, `git push` after. never `--force` unless the user said those words for this push, and then `--force-with-lease`. a push rejected for the email address: stop, and offer the host's noreply address per `/initiate` step 5.
5. paste the push output, `git log -1 --format='%h %an <%ae> %s'` and `git status -sb`, so the user sees what went and as whom.
6. a pr only if the user asked for one: `gh pr create --title <approved> --body-file <approved>`, base main. paste the url. never merge, never arm auto merge. merging is the user's.
7. the log entry: date, branch, the short sha, pushed, the pr url if any, what is open. the tbd updated. the brain if installed (`~/vault/projects/<repo>/<repo>-log.md`), else `.claude/log.md`.

after a deploy the user ran or approved, verify the served artifact (fetch the live page or bundle and grep for a string from this change), not the green checkmark. hosts rehash chunks, so comparing hashes proves nothing. merge and deploy runbooks live in `playbook`.

Wersje

RepozytoriumWynikLicencja
Ta strona · gntrs/workflow90MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
namedtoaster/the-last-mile100MIT
rjmurillo/ai-agents100MIT
ericrisco/rsc-harness100MIT
zahidakhyar/skills100MIT
NolwennD/gabier100Apache-2.0
mgiovani/cc-arsenal100MIT

Migawka bazy z 13.11.2026 · wersja paczki d40514fcec8d (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

  • 90ship-check
    Uruchamia testy i lint przed commitem lub pushem, przegląda różnicę i szuka sekretów oraz zostawionych logów debugowania.
  • 90git-commit-push
    Zapisuje commit i wypycha bieżące zmiany do repozytorium, sprawdzając wcześniej, co trafi do historii.
  • 100git-commit-push-pr
    Prowadzi od niezatwierdzonych zmian do otwartego pull requesta w jednym przepływie: commit, push i utworzenie PR.
  • 98drift-commit-push
    Przygotowuje commity i push w projekcie Drift: konwencję Conventional Commits, bramki przed pushem i to, czy push do main jest dozwolony.
  • 91commit-push
    Tworzy commit z opisem w Conventional Commits i wypycha go do zdalnego repozytorium, bez wymuszania.
  • 90ce-commit-push-pr
    Tworzy commit, wypycha gałąź i otwiera pull request wraz z opisem zmian.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.