@staff0rd/assist 0.195.3 → 0.196.1

package/README.md

@@ -41,6 +41,7 @@ After installation, the `assist` command will be available globally. You can als
 - `/draft` - Draft a new backlog item with LLM-assisted questioning
 - `/pr` - Raise a PR with a concise description
 - `/refactor` - Run refactoring checks for code quality
+- `/prompts` - Analyze denied tool calls and suggest settings changes to auto-allow recurring prompts
 - `/refine` - Refine an existing backlog item through conversation
 - `/restructure` - Analyze and restructure tightly-coupled files
 - `/review-comments` - Process PR review comments one by one
@@ -175,6 +176,7 @@ After installation, the `assist` command will be available globally. You can als
 - `assist seq query <filter> --from <date>` - Start of query window (UTC date or relative e.g. 5m, 1h, 2d)
 - `assist seq query <filter> --to <date>` - End of query window (UTC date or relative e.g. 5m, 1h, 2d)
 - `assist screenshot <process>` - Capture a screenshot of a running application window (e.g. `assist screenshot notepad`). Output directory is configurable via `screenshot.outputDir` (default `./screenshots`)
+- `assist prompts` - Show top 10 denied tool calls by frequency with count and repo breakdown
 - `assist coverage` - Print global statement coverage percentage
 - `assist complexity <pattern>` - Analyze a file (all metrics if single match, maintainability if multiple)
 - `assist complexity cyclomatic [pattern]` - Calculate cyclomatic complexity per function

package/claude/commands/prompts.md

@@ -0,0 +1,22 @@
+---
+description: Analyze denied tool calls and suggest settings changes to auto-allow recurring prompts
+---
+
+Run `assist prompts 2>&1` to get the list of most frequently denied tool calls.
+
+If there are no denied tool calls, tell the user there's nothing to fix yet and stop.
+
+Otherwise, analyze each entry and suggest specific changes to auto-allow the recurring prompts. For each entry, recommend ONE of:
+
+1. **Add a permission rule** to `claude/settings.json` `permissions.allow` — for safe, read-only commands that should always be allowed (e.g. `Bash(git log:*)`, `Bash(npm test:*)`)
+2. **Add a cli-hook allow entry** via `assist cli-hook add <cli>` — when an entire CLI's read verbs should be auto-approved
+3. **Skip** — when the denial is appropriate (write operations, destructive commands, or commands that should require confirmation)
+
+Present your suggestions as a numbered list with the specific change for each. Group related suggestions together.
+
+**Important:**
+- Only suggest allowing read-only, non-destructive commands
+- Never suggest allowing write operations (git push, rm, npm publish, etc.) without flagging them as risky
+- Reference the deny reason from the output to explain why each command was blocked
+- After presenting suggestions, ask the user which changes they'd like to apply
+- Do NOT modify `claude/settings.json` without the user's explicit approval

package/claude/settings.json

@@ -57,6 +57,8 @@
 			"SlashCommand(/seq)",
 			"Skill(inspect)",
 			"SlashCommand(/inspect)",
+			"Skill(prompts)",
+			"SlashCommand(/prompts)",
 			"Skill(screenshot)",
 			"SlashCommand(/screenshot)",
 			"Skill(draft)",