From c10bbacb64577f4555e40c73e48eead161af75f8 Mon Sep 17 00:00:00 2001 From: Paul O'Reilly Date: Tue, 17 Mar 2026 11:15:49 +1300 Subject: [PATCH] Add session log for custom-claude-skills Co-Authored-By: Claude Opus 4.6 (1M context) --- memory/log/2026-03-17.110845.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 memory/log/2026-03-17.110845.md diff --git a/memory/log/2026-03-17.110845.md b/memory/log/2026-03-17.110845.md new file mode 100644 index 0000000..420f70d --- /dev/null +++ b/memory/log/2026-03-17.110845.md @@ -0,0 +1,13 @@ +# Session Log — 2026-03-17 + +## Summary +Fixed the `/housekeeping` skill aborting mid-run because info-gathering scripts (`unreflected-logs`, `git-status-report`, `check-skills`, `validate-skill`) exit with code 1 as a status signal, which the skill's `!`command`` syntax treated as a failure. + +## Decisions +- Decision: Append `|| true` to all four bang-command invocations in the housekeeping skill — Rationale: These scripts use exit 1 to signal "issues found" (not errors), and the skill is read-only/informational, so suppressing the exit code is safe. + +## Gotchas Discovered +- **[skills]** Symptom: `!`command`` in SKILL.md fails when the command exits non-zero, even if the output is valid and informational — Fix: Append `|| true` to bang-commands that use exit codes as status signals rather than error indicators. + +## Key Context +- All four scripts in `small-scripts/scripts/` (`git-status-report`, `unreflected-logs`, `check-skills`, `validate-skill`) follow the same pattern: exit 0 = all clear, exit 1 = issues found. This is correct for CLI tools but incompatible with skill bang-command syntax without `|| true`.