Compare commits

...

1 commit

Author SHA1 Message Date
oskar c793517529 feat(kb-publish): pytaj o publikacje przy zamknieciu sesji zamiast biernego przypomnienia
Zmiana triggera z "kazda odpowiedz dotykajaca kb/" na "moment zamkniecia
sesji" (save-session, "konczymy sesje", naturalny koniec zadania). Zamiast
jednego zdania przypomnienia, CC wprost pyta operatora tak/nie o publikacje;
przy potwierdzeniu pokazuje gotowiec bash scripts/kb/publish.sh do wklejenia
(nadal nigdy nie uruchamia go sam). Brak odpowiedzi = pytanie zadane raz na
sesje, bez ponawiania.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017q2vHW4uXD8wEr7C8x87oc
2026-08-26 22:35:45 +02:00

View file

@ -1,18 +1,34 @@
--- ---
name: kb-publish name: kb-publish
description: Reminds the operator to publish the KB site after changes to kb/**/*.md. Trigger whenever this session's own edits, or a merge/diff visible in git, touch files under kb/. description: At session close, asks the operator whether to publish the KB site if kb/**/*.md changed this session. Trigger whenever the session is wrapping up (save-session, "kończymy sesję", natural end of task) and this session's own edits, or a merge/diff visible in git, touched files under kb/.
--- ---
## What this skill does ## What this skill does
At the end of your response, if this session touched `kb/**/*.md` — either Trigger point: **session close**, not every response. Session close means the
through your own edits or through a merge/diff you observed in git — append operator signals they're wrapping up — e.g. invoking `save-session`, saying
exactly one reminder sentence: something like "kończymy sesję" / "koniec na dziś" / "wrap up", or the task
reaching its natural end with no further work queued. Don't act on this skill
mid-session just because a `kb/` file was touched.
> Zmiany w kb/ — pamiętaj odpalić `bash scripts/kb/publish.sh` żeby opublikować. At that moment, if this session touched `kb/**/*.md` — either through your
own edits or through a merge/diff you observed in git — **ask the operator
directly**, as a question requiring a yes/no answer, not a passive reminder:
One sentence, no more. Don't repeat it more than once per response, and don't > Sesja dotknęła kb/. Zregenerować i zasugerować publikację (`bash scripts/kb/publish.sh`)?
add it if nothing under `kb/` changed.
- If the operator confirms (any affirmative reply): print the ready-to-paste
command block so they can copy it straight into their own shell:
```bash
bash scripts/kb/publish.sh
```
Do not run it yourself — see below.
- If the operator declines: drop it, nothing more to do.
- If the operator doesn't respond or ignores the question (moves on to
something else, ends the conversation): do **not** ask again in this
session. One ask per session, max.
## What this skill does NOT do ## What this skill does NOT do
@ -23,4 +39,4 @@ production — that is out of scope for a worktree agent and requires an
explicit, direct instruction from the operator in the current turn. explicit, direct instruction from the operator in the current turn.
If the operator explicitly asks you to run it, that instruction stands on its If the operator explicitly asks you to run it, that instruction stands on its
own — this skill only governs the passive reminder, not that request. own — this skill only governs the session-close question, not that request.