dump
/dump
Zamyka sesję i przekazuje pracę: commit i push, zwolnienie zajętych zadań PKB oraz końcowy raport.
- Autor
- nicsuzor ↗
- Repozytorium
- academicops ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.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 27.10.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 sesję i przekazuje pracę: commit i push, zwolnienie zajętych zadań PKB oraz końcowy raport.
Oryginalny opis (EN)
Session exit and handover -- commit and push work, release claimed PKB tasks, and emit a final report. Use when completing, pausing, or handing off a session.
Jak działa
- Handover Process
Podgląd SKILL.md
---
name: dump
description: Session exit and handover -- commit and push work, release claimed PKB tasks, and emit a final report. Use when completing, pausing, or handing off a session.
---
# Dump -- Session Exit
Finalize session work and provide a structured handover before exit.
## Handover Process
### 1. Save and Push Work
1. Commit all modified files. If work is incomplete, describe what is partial in the commit message.
2. Deliver commits only where the task's Output names. If Output says nothing is pushed or names only a PKB task or note, do not push. If Output names a branch or pull request, push commits to that remote branch (`git push`). Ephemeral container and session scratch paths (`<appDataDir>/brain/`, `/tmp/`, unpushed container working trees) vanish on exit; non-git evaluation datasets, specimen tables, and reports must be persisted in the PKB (via `pkb_create`, `pkb_update_body`, or `pkb_append`) with durable pointers rather than stored in ephemeral directories.
3. For pull requests (`gh pr create`), target the diverged base branch (e.g. `--base "${BASE_BRANCH:-${POLECAT_BASE_BRANCH}}"`).
4. Record the branch name and commit SHA in the final report.
### 2. Release Claimed Tasks
For each claimed task (releasing child tasks first), update the task body (`pkb_update_body` or `pkb_update_task`) so its `## Report` section records the outcome and the `premise-check` report argument (written per the `premise-check` report-form reference, asked by the task's frozen ask ids), then call `pkb_release_task` via the `services` MCP server's code-mode interface (`portal_codemode_execute` running `async () => await codemode.pkb_release_task({ id: "<task_id>", status: "<status>" })`, passing a concise 1-line `toolSummary` argument such as `toolSummary: "Release task <task_id> as <status>"`; in agy via `call_mcp_tool` with `ServerName: "services"`, in Claude Code via `mcp__services__portal_codemode_execute`) with the appropriate terminal status. Always include a 1-line `toolSummary` on all `portal_codemode_execute` calls:
- `done`: All acceptance criteria are fully met with verified evidence recorded in the task's Report section: quoted output, `file:line` citations, counts, the specimen run where requested, and the report argument answering each `<task id>/AC<n>` from that evidence. A worker whose deliverable is a PR releases `review` instead (below). An empty, template, or bare-assertion report is released as `partial`.
- `partial`: The worker's own acceptance items remain unfinished -- a scope seam, an external dependency, or a missing tool. Never release as `partial` because a dependent check (QA, merge, deploy) remains to run. Workers document what was completed and what remains unfinished in `reason` and `## Report`; workers never create or name follow-up tasks, and reports carry no 'Next task' pointer (the reconcile pass and parent epic handle next actions).
- `review`: Either the worker's PR is open and awaits merge by the repository (record `pr_url`; do not wait for CI, review or merge; `/reconcile` writes `done` on the merge), or the worker needs help to finish the task. Help is transient, never a waiting state: a worker hands back on the record, documenting what help is needed in `reason`, and never addresses or escalates to the user. Any reconcile pass reading a `review` task transitions it immediately.
- `failed`: The task cannot be completed, has reached a terminal failure, or a check failed (e.g. QA or review). Document failure evidence and root cause. Never file fix tasks or follow-up tasks; the reconcile pass notes failed tasks and decides next actions from the parent epic.
- `cancelled`: Task is obsolete or invalidated. Document reason.
- `in_progress`: Use only if an active successor session is immediately continuing work.
Task report format (for the `release_task` body update in `## Report` and the session task summary):
````markdown
### Task: <task-id> (<title>) -- <status>
- **Update**: [1-3 sentences on work completed and remaining]
- **Output**: [Branch, commit SHA, PR link, or artifact path]
- **Proof**:
```argdown
<the premise-check argdown block, asked by the task's ask ids>
```
````
The status above is the task's release status. PASS, REVISE and FAIL are the checker's verdict on this argument, recorded by whoever checks it under `## Premise-Check Verdict`; a worker never writes a verdict on its own report.
If the release tool is unavailable, record the failure trace and list claimed task IDs in the final report.
### 3. Emit Final Handover Report
Compile the overall session outcome:
```markdown
## Handover: <agent> <session-id>
1. **Task**: Task id and title.
2. **Summary**: Concise synthesis of findings and modifications.
3. **Status & Safeguards**:
- STATUS: <release status: done | partial | review | failed | cancelled | in_progress>
- GATE: <the acceptance criterion id tested, and observed result against it>
- CONFIDENCE: <high | med | low> + <what single check would falsify this>
- CONFOUND CHECK: <did a clean-room/differential control run? result? -- or "NOT RUN">
4. **Output**: <branch + commit SHA> | <PR or artifact link>
5. **Argument**: The `argdown` block recorded under the task's `## Report`.
6. **Limitations**: Unresolved items, out-of-scope elements, and verbatim error outputs.
```
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · nicsuzor/academicops | 100 | MIT |
| emaballarin/ccplugins | 100 | MIT |
| kurtosis-tech/kurtosis | 100 | Apache-2.0 |
Identyczna treść występuje jeszcze w 5 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 13.11.2026 · wersja paczki ab8da754792c (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
- 100checkpoint
Zamyka sesję jednorazowo: dziennik dnia, uzgodnienie faktów w plikach głównych, dokumentach projektu i pamięci, selektywny commit i push oraz weryfikacja zdalna, w trybie pełnym lub lite. - 100handover
Przekazuje pracę sesji nowej sesji, zbierając stan z dysku i zapisując dokument przekazania, gdy zadziała limit kontekstu. - 91pkb-search
Wyszukuje semantycznie kod i dokumenty w repozytorium przez CLI pkb, gdy trzeba zorientować się w bazie kodu, a nie znaleźć dokładny symbol. - 100commit-push-pr
Tworzy commit, wysyła zmiany do zdalnego repozytorium i otwiera pull request gotowy do przeglądu. - 100handover-document-creator
Pisze dokument przekazania sesji w .context/handovers/, aby inny agent lub sesja wznowili pracę bez odtwarzania kontekstu, gdy sesja kończy się lub jest wstrzymywana w trakcie pracy. - 90shift-change
Przekazuje bieżącą sesję nowej, pisząc notatkę przekazania z następnymi krokami, mapą myśli, odrzuconymi ścieżkami i poprawkami użytkownika.