Przejdź do treści
Biblioteka skilli
Programowanie · Automatyzacja

delivery

/delivery

Domyka dostawę zmian w Git i GitHub: walidację, bezpośrednie wysłanie lub niezależny przegląd PR oraz sprzątanie gałęzi.

Licencja
MIT
Ostatnia zmiana repozytorium
12.11.2026

Ocena i bezpieczeństwo

96/ 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ść31 / 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 12.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

Domyka dostawę zmian w Git i GitHub: walidację, bezpośrednie wysłanie lub niezależny przegląd PR oraz sprzątanie gałęzi.

Oryginalny opis (EN)

Complete Git/GitHub delivery and handoff using proportionate validation, direct delivery or independent PR review, verified fixes and authorized completion. Use when delivering changes, handing work between agents, or cleaning up delivered branches and worktrees; ordinary code browsing does not require it.

Jak działa

SKILL.md bez nagłówków drugiego poziomu · 19 linii, 659 słów

Podgląd SKILL.md
---
name: delivery
description: Complete Git/GitHub delivery and handoff using proportionate validation, direct delivery or independent PR review, verified fixes and authorized completion. Use when delivering changes, handing work between agents, or cleaning up delivered branches and worktrees; ordinary code browsing does not require it.
---

# Delivery rules

These are personal delivery defaults, reusable across agent harnesses. Read the current task and project guidance before delivery. Installation alone grants no repository access or publication, deployment or device authority. The maintained source of this skill is the personal-skills repository: change and push it there, then reinstall; never edit an installed copy alone.

- The user's explicit instruction for the current task overrides their own global, project and skill workflow defaults. If they request direct push or waive review, follow that choice even for a high-risk change. Record skipped checks honestly. Actual access restrictions and repository protections still apply; report a concrete blocker instead of inventing permission.
- Use two paths: direct delivery for bounded low-risk changes or an explicit user choice; otherwise one PR per complete goal, including multi-module and high-risk work.
- The current delivery session owns validation, independent review, verified fixes, necessary re-review and authorized merge. Do not stop at opening a PR. Use a fresh reviewer session or independent review process; review the current candidate and recheck the remote head before merging.
- Keep review focused on correctness, the request, simplicity and proportionate validation. Report evidence and practical impact; do not invent blockers. A failed or unfinished review is not a pass. Report unresolved blockers with the retained branch/PR and a concrete next step.
- GitHub is the task and code record. Reuse the existing Issue/PR; create an Issue only for substantive bugs, features or work needing continuation. Check current ownership before taking over. Small one-off changes do not need a tracking Issue just for ceremony.
- When human input is needed, state the blocker, the specific action or reply needed, and what follows. Preserve work for the next session. A comment does not automatically wake a finished agent; do not create watchers, schedules or cross-chat messages without an explicit request.
- When switching harnesses, leave the goal, completed work, remaining work and relevant branch/PR in the same task. Retain original authorship and record the new handler; avoid a second competing implementation.
- Verify the destination repository, branch and publication scope. Preserve unrelated changes and project-specific data, deployment and device permissions. A code merge does not establish installation, deployment or physical acceptance.
- At every milestone, handoff, and pause, commit verified work and push the working branch; unfinished work stays on its own branch, never as an unpushed or `no-upstream` leftover.
- Build, sign, or install a candidate only from a clean committed SHA, and tag each installed or shipped version on its commit; a dirty-tree build is a scratch test artifact, never a release.
- Safe sync is standard delivery work under an authorized task on owned private repositories: feature branches, pushed working branches, and draft or review PRs after a sensitive-content check. Force-pushes, merges to protected `main` without the required review, public/upstream/company writes outside scope, live configuration changes, deployments, and device operations keep their separate approval gates.
- Use English Issue/PR/commit text; preserve quoted source text. Include one attribution line, `Agent: <harness>/<runtime-reported-model>`, in each agent-written Issue or PR body and each individual agent-written Issue or PR comment. Before posting, check available current-session and current-turn runtime metadata for both harness and model. For Codex, when available, use `CODEX_THREAD_ID` to locate the current session record under `~/.codex/sessions/`, its `session_meta.originator` and the latest current-turn `turn_context.model`; read only the identity fields needed. In other harnesses use their available current-message, session or runtime metadata. A default, earlier turn or unsupported model self-description does not establish the current model; use configuration only when it identifies the actual model used. Use `Unknown` only for a part still unverified after checking available sources. Do not expose session contents or private host details. For a substantial PR, include a concise original session reference when available.
- After verified delivery, remove only task-created branches, worktrees and temporary files with no undelivered work, needed evidence or active use. Preserve uncertain items and state why. Keep required CI and ordinary repository maintenance.

Wersje

RepozytoriumWynikLicencja
Ta strona · Popcornnnnnnnn/personal-skills96MIT
pfangueiro/claude-code-agents100MIT
hieuphung97/dely100MIT
FlintSH/tinderbox90MPL-2.0
fabiensalles/claude-marketplace90MIT

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

  • 90project-git
    Przegląda zmiany w Git, tworzy commity i wypycha je, zapisuje dostawę w Git i obsługuje żądane aktualizacje PR lub MR.
  • 90git-github-workflows
    Prowadzi przez przepływ pracy w git i GitHub: commity, pull requesty, odpowiedzi na recenzje, worktree, wydania i sprzątanie gałęzi.
  • 100git-worktree
    Zarządza worktrees Git dla izolowanego, równoległego rozwoju: tworzenie, przełączanie i sprzątanie worktrees dla równoległej pracy nad beads.
  • 100git-worktree
    Tworzy izolowane worktrees git dla równoległych gałęzi funkcji, przeglądu PR bez naruszania bieżącego checkoutu i sprzątania starych worktrees.
  • 90git
    Wykonuje commit, pull request, scalenie lub sprzątanie gałęzi według reguł git z pliku konfiguracji użytkownika.
  • 100git-worktree
    Zarządza worktree Git: tworzy je z gałęzi lokalnych lub zdalnych, wyświetla aktywne ze szczegółami, usuwa i przełącza, aby pracować na wielu gałęziach bez stashowania 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.