task-closeout
/task-closeout
Zamyka zadanie przed zgłoszeniem ukończenia: usuwa pliki robocze, sprawdza diff pod kątem prywatnych danych i pisze przekazanie.
- Autor
- Sequela02 ↗
- Repozytorium
- canasta ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 11.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 4
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 11.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
Zamyka zadanie przed zgłoszeniem ukończenia: usuwa pliki robocze, sprawdza diff pod kątem prywatnych danych i pisze przekazanie.
Oryginalny opis (EN)
Close out a task before saying it is done; remove the scratch files it created, check the diff for private material and unsupported claims, write a handoff, or retire a branch or worktree. Use when finishing work, when asked for a handoff or session summary, or before deleting a branch. Not for where docs belong (documentation-hygiene).
Jak działa
- Done when
Podgląd SKILL.md
--- name: task-closeout disable-model-invocation: true description: Close out a task before saying it is done; remove the scratch files it created, check the diff for private material and unsupported claims, write a handoff, or retire a branch or worktree. Use when finishing work, when asked for a handoff or session summary, or before deleting a branch. Not for where docs belong (documentation-hygiene). tags: - workflow - artifacts - handoff --- # Task closeout Leave the tree with the task's useful changes and nothing else, and leave the next person what they cannot reconstruct. Apply this to the files this task created or changed; finishing a task does not authorize a repository-wide cleanup. 1. **Inventory.** Inspect the diff and new files, including untracked ones. Mark each as kept, removed, or someone else's. 2. **Stop and remove what you started.** Stop the processes, servers and watchers the task started, and close its browser tabs, also when the task failed or was cancelled. Delete task-created scratch files and generated media that have no remaining use. Keep user work and files of unknown origin until their owner and disposition are known. Never use broad clean or reset commands to make the tree look clean. Honor legal, audit, release and repository retention requirements. 3. **Check what goes public.** Review additions for private material (personal paths, credentials, session context, private project or client names, and internal infrastructure: secret-store names and what they hold, private repositories and their paths, hosts, accounts) and for completion claims no check supports. Editing published text doesn't remove it: hosts such as GitHub keep earlier versions, so delete, close and replace, or rewrite an unmerged branch. If sensitive material is already committed or published, removing the working copy does not repair it: surface it for a security response without reproducing it. 4. **Docs.** When the task touched documentation, finish `documentation-hygiene`'s close-out checks. 5. **Report.** Give the useful changes, the checks run with their results, and the material gaps in the reply. Not a new cleanup report by default. 6. **Learn from repeats.** When the same correction came up again, find why the existing feedback missed it and propose a safeguard where it belongs (a validation rule, clearer ownership, better instructions), with what it would catch and what it leaves to judgment. Get approval before adding enforcement beyond the task. Load a reference only for its task: - A handoff or session summary for whoever continues: [handoff.md](references/handoff.md). - Retiring a branch, worktree or remote ref: [branch-retirement.md](references/branch-retirement.md). Local and remote deletion each need their own explicit authorization. ## Done when - every file the task created is kept with a reason, or removed; - the diff holds no private material and no unsupported claim; - the reply lists the checks run and the gaps left. This procedure grants no publication, history-rewrite or deletion authority beyond the user's task.
Pliki w paczce (4)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
- references/branch-retirement.md 3 KB
- references/handoff.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · Sequela02/canasta | 90 | MIT |
| hypercubed/agent-knowledge-starter-kit | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki d72a027f8982 (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
- 100session-closeout
Zamyka zakończone zadanie: pisze raport końcowy SUMMARY.md, retrospektywę etapu i dokumentację w katalogu zadania. - 100worktree-handoff
Tworzy worktree dla zadania i zapisuje kontekst przekazania w pliku planu, który trafia do commita na gałęzi. - 90conductor-execution-closeout
Zamyka wdrożenie według zatwierdzonego pakietu: weryfikuje wykonanie, porównuje diff z planem i ocenia ryzyko resztkowe. - 100handoff
Pisze lub wczytuje HANDOFF.md, notatkę wznowienia, dzięki której nowa sesja albo agent w innym środowisku kontynuuje gałąź. - 100wrap-up
Zamyka małą zmianę lub wieloetapowe zadanie: sprawdza cel, bramki jakości i diff, a potem przygotowuje dowody i przekazanie. - 90finishing-a-development-branch
Prowadzi integrację lub sprzątanie istniejącej gałęzi albo worktree utworzonego dla zadania po zweryfikowanej pracy, a także scalanie, pull request i obsługę cyklu życia gałęzi na prośbę użytkownika.