fix(hooks): tell the user when a save can't add a widget's hooks - #703

Relates to #394: this covers its wrapper-script case. The issue's original cause isn't known, so this doesn't close it.

What

• The notice: when a save can't add the Claude Code hooks a widget needs (today only Skills has hooks), Ctrl+S and Save & Exit show a notice instead of "✓ Configuration saved". It names:
  • the widgets that lost their hooks;
  • the status line command;
  • how a wrapper script gets the hooks.
• Continue: returns to the screen Ctrl+S was pressed on, or exits after Save & Exit.
• Docs: a "Skills always shows none" note in docs/USAGE.md, with a pointer from the README next to the other status line notes.

Why

Skills reads skill activity that Claude Code hooks record. Since upstream #674, saving adds those hooks only when the status line command contains ccstatusline, because any other command may be another tool's script, and Claude Code adds UserPromptSubmit output to the prompt. That rule stays.

Its cost is a wrapper such as bash ~/.claude/status.sh that runs ccstatusline inside. It gets no hooks:

• the save still says "✓ Configuration saved";
• Skills shows none for good;
• nothing tells the user why, which is what Skill is always "none" #394 reports.

The fix for such a wrapper is easy once you know it. I checked it with the built CLI under Bun and Node:

• a script named ~/.claude/ccstatusline-wrapper.sh running ccstatusline "$@";
• run as bash ~/.claude/ccstatusline-wrapper.sh --hook with a UserPromptSubmit payload for /commit;
• it logged the skill.

How

• syncWidgetHooks returns the hooks it left out, { statusCommand, widgetNames }, or null. It returns null when:

  • every needed hook was added;
  • no widget needs a hook;
  • no status line is installed yet (installing ccstatusline adds the hooks, as before).

  The rule itself is unchanged and stays in hooks.ts.

• saveSettings passes that result on. A failed hook sync still counts as a successful save, and returns null.

• App.tsx:

  • Both save paths show the existing FlowNotice (as Install Complete does) when hooks were left out.
  • A notice's continueScreen can be 'exit', so Save & Exit's notice closes the TUI on Continue.
  • Ctrl+S pressed on a notice returns to the main menu.
  • FlowNotice's props leave out continueScreen, which only App reads, in onContinue.

Demo

With Claude Code's status line set to bash ~/.claude/statusline.sh, saving a line that has Skills shows the notice, and Continue returns to the main menu.

Powerline

Plain

Testing

• hooks.test.ts:
  • The other-tool case returns { statusCommand, widgetNames: ['Skills'] }.
  • A shell-wrapped ccstatusline command returns null.
  • Two new cases: no widget needs hooks, and no status line installed.
• config.test.ts: a new case checks that saveSettings returns the left-out hooks.
• App.test.ts (Ink, waiting for each key's effect):
  • Ctrl+S on Edit Lines shows the notice, and Continue returns to Edit Lines.
  • Save & Exit saves, shows the notice, and Continue exits.
  • Both passed 12 runs in a row.
• Full suite and lint: bun test 3117 pass, 0 fail; bun run lint passes.
• Node (Vitest): the three changed test files pass 64 of 64.
• Built CLI under Bun 1.4.2 and Node 26.10.0:
  • Piped renders agree across runtimes and match main in plain and Powerline modes.
  • The TUI opens and exits cleanly.