From edf2022e07787bb8e459050c43ee1ca963d7c5fb Mon Sep 17 00:00:00 2001 From: EthanHuo Date: Fri, 13 Nov 2026 00:35:44 +0800 Subject: [PATCH] docs(agents): update the user's local sigil after every change A change is done when the user's installed sigil runs it, not when it merges: agents run update-local-tool and report before -> after. --- AGENTS.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 AGENTS.md diff --git a/AGENTS.md b/AGENTS.md new file mode 100644 index 0000000..29183c9 --- /dev/null +++ b/AGENTS.md @@ -0,0 +1,17 @@ +# sigil + +## Local install after every change + +On the user's machines `sigil` is the release bundle in `~/.local/bin`, +installed by the workspace `update-local-tool` skill. A change is not done when +it merges or releases. It is done when the user's local `sigil` runs it. The +user does not watch for this, so do it without being asked: + +1. After the release workflow for your change succeeds, check whether the tool is + installed: `command -v sigil`. If it is not, stop here. +2. Run `bash ~/workspace/.agents/skills/update-local-tool/update.sh sigil`. It prints `before -> after`. +3. Check your change with the installed binary, for example `sigil @schema` or the + command you changed. +4. Put the `before -> after` line in your final report. + +If the release failed, report that. Don't install a local build in its place.