Automatyzuje kroki 2-3 z kb/runbooks/kb-site-deploy.md (generacja, kontrola wyciekow, upload przez helper alpine, smoke test) w jednym fail-closed skrypcie zamiast recznego klikania. Runbook zaktualizowany, zeby referencjonowal skrypt, z zachowaniem wyjasnien co/dlaczego dla kazdej bramki. Dodaje skill kb-publish, ktory przypomina operatorowi o publikacji po zmianach w kb/**/*.md, ale nigdy sam nie uruchamia skryptu (dotyka prod przez SSH). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
---
|
|
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/.
|
|
---
|
|
|
|
## What this skill does
|
|
|
|
At the end of your response, if this session touched `kb/**/*.md` — either
|
|
through your own edits or through a merge/diff you observed in git — append
|
|
exactly one reminder sentence:
|
|
|
|
> Zmiany w kb/ — pamiętaj odpalić `bash scripts/kb/publish.sh` żeby opublikować.
|
|
|
|
One sentence, no more. Don't repeat it more than once per response, and don't
|
|
add it if nothing under `kb/` changed.
|
|
|
|
## What this skill does NOT do
|
|
|
|
**Never run `scripts/kb/publish.sh` yourself**, under any circumstances, even
|
|
if the operator's task prompt says to deploy, publish, or calibrate. The
|
|
script SSHes into PIHA and overwrites the live `kb-site` content volume on
|
|
production — that is out of scope for a worktree agent and requires an
|
|
explicit, direct instruction from the operator in the current turn.
|
|
|
|
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.
|