[Bug] Inaccurate skill documentation: find misclassified as unconditionally auto-allowed

Resolved 💬 0 comments Opened Jun 3, 2026 by kportertx Closed Jun 4, 2026

Bug Description
Title: fewer-permission-prompts skill misdescribes find as "always auto-allowed (any args)" Body: The bundled /fewer-permission-prompts skill (Claude Code 2.1.161) lists find under "Always auto-allowed (any args)" in its step-4 reference of commands that never prompt. This is inaccurate and potentially misleading. The actual bash read-only validator correctly gates find — its auto-allow regex uses a negative lookahead excluding -delete -exec -execdir -ok -okdir -fprint -fprint0 -fprintf -fls -files0-from (and rejects shell metacharacters), so find . -exec ... \; and find -delete do prompt. The implementation is fine; the skill doc is wrong. Impact: Anyone following the skill's guidance could wrongly conclude that find -delete/-exec won't prompt, or (when curating allowlists) reason about find as unconditionally safe. Fix: Move find out of the "any args" list into the conditional category alongside sed — e.g. "find — read-only unless -exec/-execdir/-ok/-okdir/-delete/-fprint/-fls/-files0-from present."*

Environment Info

  • Platform: linux
  • Terminal: gnome-terminal
  • Version: 2.1.161
  • Feedback ID: 3ccd63b0-5dcb-4cba-9e33-456c11074d9a

Errors

[]

View original on GitHub ↗