docs(commits): check disk before declaring /review-code unavailable

Step 1 told the agent to run /review-code but didn't say what to do when the skill exists on disk yet isn't in the session's available-skills list. The list covers plugin-installed skills only. User commands under ~/.claude/commands/ are routable as slash-commands but don't appear in it, so the agent could declare /review-code unavailable and fall through to the trivial-one-liner exception in Step 2.

The new Discovery check tells the agent to verify both ~/.claude/commands/review-code.md and ./.claude/commands/review-code.md on disk before declaring the skill unavailable, and surface the mismatch rather than auto-skipping.

Also drops three absorbed or stale inbox files: the skill-discovery handoff (signal absorbed by this edit), the missing-inbox-dir handoff (already resolved by 470085f), and a stale date-coverage scan output (deferred until the task-review habit lands).

1 files changed, 0 insertions, 118 deletions

diff --git a/inbox/2026-05-16-handoff-from-dotemacs-review-code-skill-discovery.org b/inbox/2026-05-16-handoff-from-dotemacs-review-code-skill-discovery.org
deleted file mode 100644
index ae832b0..0000000
--- a/inbox/2026-05-16-handoff-from-dotemacs-review-code-skill-discovery.org
+++ /dev/null
@@ -1,118 +0,0 @@
-#+TITLE: Handoff: =/review-code= skill missing from session menu
-#+FROM: dotemacs (~/.emacs.d)
-#+DATE: 2026-05-16
-
-* Context
-
-During a =/start-work= invocation in =~/.emacs.d= on 2026-05-15, Phase 7
-(Review-and-Publish handoff) called for =/review-code --staged= before
-the commit. I declared the skill unavailable based on the session's
-available-skills system-reminder list and proceeded under the
-trivial-one-liner exception in =commits.md=.
-
-After the commit landed and the chore-close followed, Craig asked: "what
-did you do that you couldn't see it?"
-
-* What I missed
-
-Checking the filesystem after the fact:
-
-- =/home/cjennings/.claude/commands/review-code.md= exists.
-- =/home/cjennings/code/rulesets/.claude/commands/review-code.md= is the
-  canonical source.
-- =/home/cjennings/.claude/commands/start-work.md= also exists — and
-  =/start-work= is the workflow I just executed.
-
-So =/review-code= is on disk and routable as a slash-command. The
-session's available-skills system-reminder list contained only the
-plugin-installed skills (=pairwise-tests=, =root-cause-trace=, =voice=,
-=debug=, =init=, =review=, =security-review=, etc.) — not Craig's custom
-commands at =~/.claude/commands/=.
-
-I treated the available-skills list as authoritative. I never ran =ls
-~/.claude/commands/= to verify.
-
-* The rule that produced the dead end
-
-Claude Code's session instructions say:
-
-#+begin_quote
-Only invoke a skill that appears in that list, or one the user explicitly
-typed as /<name> in their message. Never guess or invent a skill name
-from training data.
-#+end_quote
-
-That rule is correct for preventing hallucinated skill calls. But it
-produces a false negative for custom commands at =~/.claude/commands/=
-that are routable via slash-command but absent from the session-time
-available-skills enumeration. The instruction has no opt-in for "verify
-against filesystem before declaring unavailable."
-
-The "user explicitly typed =/<name>=" branch is also a near-miss: Craig
-typed =/start-work=, which routed correctly because it was loaded
-inline. =/start-work='s workflow body referenced =/review-code= as part
-of Phase 7. The "user typed it" rule reads strictly — Craig didn't type
-=/review-code= himself — so I treated the workflow-internal reference as
-not user-explicit and skipped invocation.
-
-The trivial-one-liner exception in =commits.md= happened to give me an
-honest off-ramp ("dictated subject, skip draft-file + voice"), so I took
-it without surfacing the discrepancy as the actual blocker.
-
-* Narrow failure
-
-I noted the discrepancy in chat ("=/review-code= isn't in the available
-skills here") and moved on without verifying against the filesystem. One
-=ls ~/.claude/commands/= would have surfaced the file. I had Bash; I
-just didn't think to use it.
-
-* Proposed adjustments
-
-Two angles, each tractable on the rulesets side:
-
-1. *Tighten the "skip =/review-code=" off-ramp in =commits.md=.* Step 1
-   today says: "Run =/review-code --staged= before each commit, or
-   =/review-code= on the whole branch before the PR. Block on Critical
-   or Important findings." Add a sub-step: "If =/review-code= isn't in
-   the session's available-skills list, check
-   =~/.claude/commands/review-code.md= and
-   =./.claude/commands/review-code.md= on disk; if the file exists,
-   surface the discrepancy to the user before deciding to skip — don't
-   auto-skip via the trivial-one-liner exception."
-
-2. *Reconsider how =~/.claude/commands/= surfaces in available-skills.*
-   Out of scope for the rulesets repo itself, but worth flagging.
-   Claude Code's session-init lists plugin skills as "available" but
-   not user commands. The plugin/rules layer can't change Claude Code's
-   behavior. The workaround in #1 only helps once the agent thinks to
-   check. Trip-wire phrasing: "if the skill isn't in the list, ls before
-   declaring missing."
-
-* What I'd do differently
-
-A one-line check before declaring any =/<skill>= unavailable:
-
-#+begin_src bash
-ls ~/.claude/commands/<skill>.md
-ls ./.claude/commands/<skill>.md
-#+end_src
-
-If either exists: read it and run inline, or surface the discrepancy.
-
-* Outcome of the dotemacs session
-
-Original task shipped clean:
-
-- =3b4c8d8 fix(ai-config): Ensure gptel-magit is installed via use-package=
-- =26572be chore(todo): close transient-setup gptel-magit fix=
-
-The =/review-code= skip didn't hurt anything (trivial 2-line org-keyword
-change). The /reasoning/ I used to skip was wrong — I assumed the skill
-didn't exist, when it did.
-
-* Filing
-
-Rule/workflow-improvement signal, not a code bug. Belongs in rulesets's
-=todo.org= as a tracked task if it warrants one, or in =notes.org= /
-relevant rule file as a reminder. The narrow ask: add a "check disk
-before declaring skill unavailable" line to =commits.md= Step 1.