reviewlisted

Batch-promote frequently-asked tool-gates patterns to permanent permission rules in settings.json. Lists pending approvals (commands the user approved one-time through the prompt, accumulated across sessions), shows counts and suggested glob patterns, multi-selects to write at user/project/local scope. Use after several sessions to triage what's piled up, or to share patterns across projects. For single-prompt approvals the user should usually click 'Yes, and don't ask again for X' in the CC prompt instead. It covers the in-session case organically since tool-gates defers benign asks. NOT for manual settings.json edits, hooks, env vars, or MCP config (use update-config). NOT for scanning a transcript to build an allowlist from scratch (use fewer-permission-prompts). When the user wants to triage their pending approval queue, batch-promote frequently-asked patterns to permanent rules, share approvals across projects, or audit what's accumulated. Triggers on 'review pending', 'pending approvals', 'tool-gates re
camjac251/tool-gates · ★ 4 · AI & Automation · score 60

Install: claude install-skill camjac251/tool-gates

# Review Pending Approvals Promote pending one-time approvals into permanent settings.json rules. Single-shot in-session approvals already work via the CC prompt's "Yes, and don't ask again for X" button (tool-gates defers benign asks so CC's resolver populates the prefix suggestion). This skill is for the cross-session cleanup pass. ## Steps 1. Run `tool-gates pending list --project` to fetch the current project's queue. - This skill defaults to project scope by passing `--project`. - If `$ARGUMENTS` contains `--all`, run `tool-gates pending list` instead to fetch every project. 2. If the queue is empty, tell the user and stop. 3. Present a numbered checklist using the most-specific suggested pattern per row: ``` 1. [ ] cargo build --release (12x) -> cargo build:* 2. [ ] npm install (8x) -> npm install:* 3. [ ] git push origin main (3x) -> git push:* ``` When a row has multiple patterns, mention broader alternatives briefly. Example: "row 3 could use the broader `git:*` if you also want force-push allowed." 4. Ask which to approve and at what scope: - **local** (default): just this project, just this user. Writes to `.claude/settings.local.json` (gitignored). - **project**: shared with the team via git. Writes to `.claude/settings.json`. - **user**: every project on this machine. Writes to `~/.claude/settings.json`. 5. For each selection, run `tool-gates approve '<pattern>' -s <scope>`. 6. Show the final state with `too