permissions-review

Review session transcripts and update Claude Code's Bash command permission allowlist.

3|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/MaxWolf-01/agents --skill permissions-review-maxwolf-01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: permissions-review
Source: https://github.com/MaxWolf-01/agents/tree/main/mx/skills/permissions-review
Command: npx skills add https://github.com/MaxWolf-01/agents --skill permissions-review-maxwolf-01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tyro, and includes scripts (resource) components.

What problem does it solve? Repeated permission prompts for harmless Bash commands interrupt agent workflows. This Skill scans recent Claude Code session transcripts for commands that triggered prompts, classifies them against a safety bar, and applies allowlist additions to global or project settings files. ## Core Features & Use Cases - Session Scanning: Parses JSONL session transcripts, splits chained shell commands per segment, and counts which command signatures would prompt under the current allowlist. - Safety Classification: Separates read-only commands safe to allowlist from state mutations and arbitrary code execution patterns that must stay gated, flagging judgment calls for the user. - Settings Management: Splits additions between global and project-local settings.json files, deduplicates entries, and commits each change to its repository. - Use Case: After a week of agent sessions, run the review to discover that docker compose logs and npm run check prompted dozens of times, then allowlist the safe ones so future sessions run uninterrupted. ## Quick Start Ask the agent to review recent sessions for permission prompts and update the Claude Code allowlist with safe commands.

Frequently Asked Questions about permissions-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce Claude Code permission prompts for Bash commands?

Scan recent session transcripts for commands that prompted, then add safe read-only patterns to the permissions.allow list in settings.json. The scanner script reports each blocked command signature with its frequency so you can allowlist the recurring ones.

How does Claude Code match commands against the allowlist?

Claude Code splits commands on pipes, semicolons, && and ||, then matches each segment independently against Bash() patterns in settings.json. Globs span spaces, and a trailing * requires at least one argument, so bare commands need their own entry.

Which commands are safe to add to the Claude Code allowlist?

Pure reads, diagnostics, type checkers, and log viewers are safe to allowlist. Never allowlist state mutations like git commit, docker rm, or npm install, and never wildcard interpreters or task runners since that permits arbitrary code execution.

Why does a command not prompt even though it is missing from settings.json?

Claude Code auto-approves a built-in set of read-only programs like cat, grep, and git status without consulting settings.json. Run the scanner with --show-auto-approved to see which commands the built-in set absorbed.

Should allowlist entries go in global or project settings?

Universal read-only commands belong in the global ~/.claude/settings.json, while project-specific make targets and domain tools belong in the project's .claude/settings.json. Remove local entries already covered globally and promote entries that are project-agnostic.