Przejdź do treści
Biblioteka skilli
AI i agenci · Automatyzacja

th-clear

/th-clear

Przenosi sesję do świeżego kontekstu w tym samym terminalu: zapisuje punkt kontrolny, uzbraja wznowienie i pokazuje polecenie.

Repozytorium
smooth ↗
Licencja
MIT
Ostatnia zmiana repozytorium
27.10.2026

Ocena i bezpieczeństwo

100/ 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ść35 / 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 27.10.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

Przenosi sesję do świeżego kontekstu w tym samym terminalu: zapisuje punkt kontrolny, uzbraja wznowienie i pokazuje polecenie.

Wyzwalacze z opisu

s /th-clear suggestion, or the user saysfresh contextth-clearcontext is getting big
Oryginalny opis (EN)

Hand this session off and continue in a fresh context in the SAME terminal — the th-handoff checkpoint, then `th harness handoff arm`, then the user types `/clear` and `/th-handoff resume <pearl>` (the armed token usually resumes on its own). Invoke as `/th-clear [pearl-id]`. Use when the user accepts the budget hook's /th-clear suggestion, or the user says "clear and continue", "fresh context", "th-clear", or "context is getting big".

Jak działa

  1. Steps
  2. Notes
Sekcje z nagłówków SKILL.md, w oryginale · 35 linii, 616 słów
Podgląd SKILL.md
---
name: th-clear
description: Hand this session off and continue in a fresh context in the SAME terminal — the th-handoff checkpoint, then `th harness handoff arm`, then the user types `/clear` and `/th-handoff resume <pearl>` (the armed token usually resumes on its own). Invoke as `/th-clear [pearl-id]`. Use when the user accepts the budget hook's /th-clear suggestion, or the user says "clear and continue", "fresh context", "th-clear", or "context is getting big".
---

# th-clear — hand off, clear, keep going

`/th-handoff` moves work to a session the user starts by hand. `/th-clear` is the same handoff for the common case: **this terminal, fresh context, keep going.** You can't clear your own context — only the user's `/clear` can — so this skill does everything up to that keystroke and arms a one-shot resume. The next session's SessionStart hook (`th harness handoff claim`) finds it and injects the handoff. A `/clear` with nothing armed stays a plain `/clear`.

**When it comes up.** The `th harness budget` hook never blocks. Auto-compaction is the default reset: the harness compacts at `harness.context_budget` (300k; `th harness enable` sets it) and the pearl handoff is re-injected, so keep working through a big context. Past `harness.context_suggest` (150k), finishing a piece of work — a merge or a pearl close — asks you once per context segment to mention `/th-clear` in your final report, only if the user's task is done. Never stop mid-task to suggest it. Run this skill when the user asks for it, or when the hook tells you to with `harness.context_reset = clear`.

## Steps

1. **Pick the pearl.** The user-named one; else the in-progress pearl this work is on (`th pearls list --status=in_progress`, the id in the branch name); else create one exactly as `/th-handoff` step 1 does. Several pearls in flight → arm each (`--pearl` repeats, max 3).

2. **Do the th-handoff steps 2–4** (gather facts, get workers to push, write the note). Same discipline, same note sections. Be brief where the work is simple; the next session is you with an empty context, so `--next` must be the exact first action.
   `th pearls checkpoint <pearl> --note "$NOTE" --next "<first action>"`
   Build `NOTE` in a quoted heredoc (`NOTE=$(cat <<'EOF' … EOF)`) — never backticks in a double-quoted string.

3. **Read it back:** `th pearls show <pearl> --handoff`. If the fresh session would get it wrong from that text alone, checkpoint again.

4. **Arm:** `th harness handoff arm --pearl <pearl> --harness claude-code` (in Codex/OpenCode/others, pass that harness's name). It warns if the pearl has no checkpoint — fix that, don't ignore it. This terminal can claim the token for 24 hours. Arming prints the `/clear` + resume lines and copies the resume line to the clipboard.

5. **Stop and give the user the two lines `arm` printed**, copy-pasteable, plus where it picks up:
    ```
    /clear
    /th-handoff resume <pearl>
    ```
    `Picks up from: <next>.` Then end your turn. Do no more work: anything after the checkpoint is lost to the next session.

## Notes

- **In-process subagents die on `/clear`.** They must push and checkpoint before step 4, exactly as in `/th-handoff`.
- **Why the explicit resume line:** the armed token usually resumes the fresh session by itself (the SessionStart hook injects the handoff after `/clear`), but a hook can add context, not start a turn, and an expired or missed token leaves nothing injected. `/th-handoff resume <pearl>` works either way; if the handoff was already injected, it just re-reads the same pearl.
- **Changed your mind?** `th harness handoff disarm` drops the token; `th harness handoff list` shows what is armed.
- **Relaunch instead of `/clear`** (quit, then `claude` in the same directory within the hour) also resumes, when exactly one token is armed there.
- **Missed claim?** A fresh session that finds a token it can't take (expired, another terminal's) gets a note naming the pearl instead of silence. The resume line always works.
- **Other harnesses:** the same two commands work anywhere; the harness's clear is `/clear` or `/new`. Where no SessionStart hook claims the token, the fresh session can claim by hand: `th harness handoff claim --format text`.

Wersje

W bazie nie ma innych skilli o nazwie th-clear.

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

  • 100th-handoff
    Przekazuje pracę agenta do nowej sesji bez utraty danych: zapisuje punkt przekazania, wypycha niezapisane zmiany i podaje polecenie wznowienia.
  • 90repack
    Zapisuje przekazanie na kolejną sesję, a potem prowadzi użytkownika przez /clear i /continue w czystym oknie kontekstu.
  • 86handoff
    Pisze lub aktualizuje plik HANDOFF.md, aby nowy agent mógł kontynuować pracę bez utraty kontekstu.
  • 90handoff
    Pisze dokument przekazania, by inny agent lub nowa sesja mogła kontynuować pracę bez ponownego tłumaczenia.
  • 84handoff
    Zapisuje punkt zapisu w trakcie sesji do wznowienia po /clear: trwały plik handoff albo prompt do wklejenia.
  • 90checkpoint
    Zapisuje punkt kontrolny pracy w sesji, by inny agent mógł ją podjąć po wyczyszczeniu kontekstu.

Uwagi i zgłoszenia

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